[REPO-3667] Renditions: Transform event producer Created: 17-Jul-18  Updated: 11-Jun-20  Resolved: 15-Oct-18

Status: Done
Project: Repository
Component/s: Repository, Transformations
Affects Version/s: None
Fix Version/s: Community 6.1.1, VB: AWS Migration: Transforms

Type: Epic
Reporter: Alex Mukha Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
Related
is related to by REPO-3670 Renditions: Transition to full use of... Open
Epic Name: Renditions: Transform event producer
Work Funnel: Feature
Story Points: 0
Template:

 Description   

This epic is about creating the initial version of the rendition code producing events for the Transform Service. It will be part of the alfresco-repository project, but code should be written with the goal of it being extracted into separate microservices (REPO-3671). Also see the initial and end state diagrams attached to REPO-3646.

List of goals/stories:

  • List currently supported transforms in 6.0
    Those currently supported by 6.0 without additional AMPs.
    Used to identify when the local transforms will be used and to help identify which transforms should be implemented by the Transform Service.  
  • Create dictionary of supported Transform Service transforms
    • May be a hard coded list
    • Must include the options for each transform.
  • Switch to call renditions in Transform Service
  • Event client code (transaction aware produce and consume messages)
  • Docker dev/build deployment with a queue
  • Event producer
  • Record Heart Beat date in rendition V1 REST API
  • Helm deployment includes queue by default
  • Content update policies produce events for Transform Service
  • Deprecation of public Java APIs 
  • Include Transformation Service into docker-compose and Helm
  • add integration tests (acs-packaging and acs-deployment)

Out of scope:

  • It might be required to produce a txt rendition of every index-able content by default. Can be done as onContentCreate policy that will trigger an event for the Transform Service. The TransformCreated event can be generated for Solr to consume.

Generated at Tue Aug 11 23:45:29 BST 2020 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.