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

Bulk Import job status not changed after activation #6451

Open
volodymyr-korzh opened this issue Nov 7, 2024 · 0 comments · May be fixed by #6452
Open

Bulk Import job status not changed after activation #6451

volodymyr-korzh opened this issue Nov 7, 2024 · 0 comments · May be fixed by #6452
Assignees

Comments

@volodymyr-korzh
Copy link
Collaborator

To Reproduce

  1. Create BulkImportJob
  2. Mark job As ready for activation
  3. Activate BulkImportJob

Expected behaviour
BulkImportJob status changed to RUNNING. Activating ready jobs again doesn't trigger new job.

Expected behaviour
BulkImportJob status stays READY. Activating ready jobs again triggers new job.

BulkImportJobJson job = new BulkImportJobJson();
job.setProcessingMode(JobFileRowProcessingModeEnum.FHIR_TRANSACTION);
job.setJobDescription("testFlow_TransactionRows");
job.setBatchSize(3);
String jobId = bulkDataImportSvc.createNewJob(job, files);
bulkDataImportSvc.markJobAsReadyForActivation(jobId);

ActivateJobResult activateJobOutcome = bulkDataImportSvc.activateNextReadyJob();
assertTrue(activateJobOutcome.isActivated);
// validate that job changed status from READY to RUNNING
assertEquals(BulkImportJobStatusEnum.RUNNING, bulkDataImportSvc.getJobStatus(jobId).getStatus());
@volodymyr-korzh volodymyr-korzh self-assigned this Nov 7, 2024
@volodymyr-korzh volodymyr-korzh linked a pull request Nov 7, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant