-
Notifications
You must be signed in to change notification settings - Fork 528
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
Remove legacy export job worker #4838
base: main
Are you sure you want to change the base?
Conversation
…no other possibility. Remove unused variables from CosmosFhirOperationDataStore
…ExportJob. Modified unit test in CosmosDBInitializationTests to appropriately check for all incoming list of sp's
if (IsLegacyJob(id)) | ||
{ | ||
// try old job records | ||
var oldJobs = (ILegacyExportOperationDataStore)this; | ||
return await oldJobs.GetLegacyExportJobByIdAsync(id, cancellationToken); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LTA-Thinking FYI, just want to confirm if you think this should be ok to delete? Its been a long while since old jobs were created
// try old job records | ||
var oldJobs = (ILegacyExportOperationDataStore)this; | ||
return await oldJobs.CreateLegacyExportJobAsync(jobRecord, cancellationToken); | ||
return await base.CreateExportJobAsync(jobRecord, cancellationToken); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we are only calling the base, we shouldn't need the override at all
Description
Remove all classes, stored procedures and configurations related to Legacy export job worker.
Related issues
Addresses issue #4750.
Testing
Unit tests were executed.
FHIR Team Checklist
Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)