Changes:
Updates applicable to both persistence providers
ac69f9b Fix is longer than a day set logic (#2500)
- DateTimeSearchParam and TokenDateTimeCompositeSearchParam has a column IsLongerThanADay & IsLongerThanADay2. IsLongerThanADay was always getting set to 0 and now will be set to 1 when applicable.
Updates applicable to SQL implementation only
7d03ab1 Use retryable wrappers instead of using SqlConnection string (#2504)
- Health check was using SqlConnection string to create its own SqlConnection and SqlCommand which fail with transient errors. We moved the logic to use the retryable wrappers.
5eddc23 Personal/peizhou/fiximportperfissue (#2499)
- This will fix the perf issue in import caused by low-effiency distinct function in search parameter generator.
20432e9 Bypass not FHIR request for import lock (#2495)
- Fixes Bypass not FHIR request (CustomError) for import lock.
9f45588 SQL timeout is returning a 500 error (#2497)
- SQL Timeout should return a FHIR OperationOutcome with http status 408 (Request Timeout)
Test Updates
90b08e5 fix search tests - mark as skippable (#2510)
- Given A Search Parameter with Multiple Base Resource Types. When Targeting Reindex Job to same list of Resource Types_ then search Parameters marked fully Indexed as skippable fact.
1ff1856 Fix search tests (#2503)
- Logging collection contents while validating the bundle. This could help while investigating failed test cases where the count doesn't match the expected collection count.
- When the reindex job completes, we search for resources using the new parameter. In the case of multiple instances of the fhir-server running, it could take some time for the search parameter/reindex updates to propagate to all instances. We have added some retries to account for that delay.
0e66ac2 Record exception if SearchParameterStatus out of sync with resource (#2468)
- It is possible with failures during certain race conditions between multiple FHIR instances to get the SearchParameterStatus out of sync with the underlying SearchParamterResource object. Currently the service throws an exception, but we will now log the error.
- Also added integration tests which replicate the issue.
d299e3f Check tag value for history tests (#2491)
- History tests were failing in the CI pipeline due to multiple tests creating different resources during the same time causing the mismatch with the history query count.
- This fix filters the response with the matching tag value in the test.
This list of changes was auto generated. These changes were included in the March release of Azure Health Data Services and the Azure API for FHIR.