Support Calling the Import Export Content as a Job from the new REST Endpoint and Job Queue

[fabrizzio-dotCMS]

Parent Issue

#29575

User Story

As part of the job management system, we need to integrate the existing import and export functionality as a Job that can be called via the new REST endpoint. The current logic in src/main/java/com/dotmarketing/util/ImportUtil.java must be preserved and reused as much as possible. Additionally, we need to address the memory handling issue when importing large files, ensuring that the entire file is not loaded into memory at once.

The Task should be callable from the new endpoint build in the Epic

Acceptance Criteria

1. The import and export jobs can be created and enqueued using the /jobs endpoint.
2. The status of these jobs can be queried and monitored.
3. Jobs can be canceled and retried as needed.
4. Even if the job fails and a rollback is triggered within the Job execution context. This should not affect the parent transaction that controls JobQueueManager

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

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

Tasks

Preview Give feedback

1. Create BufferedCsvReader to Handle Large CSV Files #29487
   Team : Scout Triage Type : Task +3
2. Create a Job with the relevant logic from ImportUtil and ImportContentletsAction to successfully import large files #29498
   NW Removed QA : Approved QA : Passed Internal Release : 24.11.25 Team : Scout Type : Task +6

[github-actions]

PRs:

• fix(jobQueue) Postman should use JWT Refs: #29482 #30362

[nollymar]

We have to make sure that it is possible to import/export large data sets.

This issue is preventing us from exporting large pieces of content