Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
2 tasks
fabrizzio-dotCMS opened this issue Aug 7, 2024 · 0 comments

Comments

@fabrizzio-dotCMS
Copy link
Contributor

fabrizzio-dotCMS commented Aug 7, 2024

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

  1. Team : Scout Triage Type : Task
  2. Team : Scout Triage Type : Task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Next 1-3 Sprints
Development

No branches or pull requests

2 participants