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

Remove legacy export job worker #4838

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

paorodma-ms
Copy link

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

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

…no other possibility. Remove unused variables from CosmosFhirOperationDataStore
…ExportJob. Modified unit test in CosmosDBInitializationTests to appropriately check for all incoming list of sp's
@paorodma-ms paorodma-ms requested a review from a team as a code owner February 24, 2025 14:55
Comment on lines -114 to -120
if (IsLegacyJob(id))
{
// try old job records
var oldJobs = (ILegacyExportOperationDataStore)this;
return await oldJobs.GetLegacyExportJobByIdAsync(id, cancellationToken);
}

Copy link
Member

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);
Copy link
Member

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

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 this pull request may close these issues.

2 participants