generated from CDCgov/template
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
DASB-234 - Implement report counts data projection (#58)
* Code cleanup * Start of hl7v2 counts implementation * More detailed counts by stage name * Optimized counts query and logic * Renamed endpoint to be generic for getting report counts * Send hl7 messages in a batch * Updated service bus library to latest * Add retry logic for persisting reports to cosmosdb * Create report retries rework * Added constants for default retry interval and max retries * Added more logging to creating reports * Fixes to creating reports logic * Added uploadId to creating report log messages * Added calculated backoff interval based on retry number * Fixed bug in retry interval when status code unknown * Added more useful links to comments surrounding cosmosdb 429s * Updated azure cosmos library to 4.55.0 * Name changes in counts endpoint to be more generic * Create initial container with 50000 R/Us * Added new endpoint for getting counts with query params * Set R/Us back to 1000, the minimum * Updated upload status to use new content format in reports * Code cleanup * Fixed timestamp and double to long number policy with json conversions * Don't show time uploading when metadata verify failed * Fixed bug with wrong stage report id returned when creating a report * Moved aggregate summary class to its own file, added class comment header * Special counting based on schema name in progress * Code cleanup * Special counting based on schema name working for aggregate counts as well * Code cleanup * Get counts for structure validation summary results * Code cleanup * Updated postman and openapi spec for new counts endpoints --------- Co-authored-by: Matt B Krystof <[email protected]>
- Loading branch information
Showing
23 changed files
with
1,096 additions
and
121 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.