Spike: Import/Export content as a job

[nollymar]

Parent Issue

No response

Task

Currently, importing and exporting content using large CSV files is a cumbersome process, especially for performance reasons. The import/export logic is executed through an action that internally keeps in memory all the data needed to be processed.

We would like to provide an endpoint that can trigger an import/export execution through jobs, like a job processor. This endpoint should be able to:

• Expose a method to trigger an import/export and provide a job id
• Return a job status given a job id or a list of job ids

The job processor can be implemented as a generic processor that might be used in the future to scale other features, not just the Import/Export functionality.

Scope of this task

• Research and select the technology to be used to manage the job queue
• Identify the changes required to be made in the ImportExportAction logic
• Break down the tasks required to implement the endpoint

Acceptance Criteria

• Define one epic with the subtasks required to implement the endpoint
• Define one epic with the subtasks required to support calling the import/export logic using jobs

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

Acceptance Criteria

No response

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[fabrizzio-dotCMS]

Epics:
REST Endpoint and Job Queue Abstraction
Import Export Content as a Job