This repository has been archived by the owner on Sep 6, 2023. It is now read-only.
Multi company parallel exports #47
Merged
Conversation
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
…iCompanyParallelExports
…iCompanyParallelExports
* Changed field name * Adding pending tables feature * restoring the deleted fields as obsolete * when data canot be exported, JQ fails Co-authored-by: Soumya Dutta <soudutta@microsoft.com>
…iCompanyParallelExports
…osoft/bc2adls into MultiCompanyParallelExports
added 8 commits
October 7, 2022 15:25
…not have changed since.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The ability to simultaneously export data from multiple companies has been introduced. This is expected to save time and effort in cases which required users to sequence the runs for different companies one after the other. The key is addition of a flag on the setup table and ensuring that no export schema changes are allowed as long as this new flag is set.
Tracking export sessions per company as well, as 2 sessions could be exporting the same table in different companies.
Revisited telemetry and added detailed verbose telemetry. Also telemetry has been classified as SystemMetaData, as no customer data from the tables is actually being logged.
The Running flag in the setup table was used previously to track ongoing sessions. This field has been removed as it was a performance issue to place a lock in order to change it via different sessions. Also gone are the fields that used to track states of last runs. A new table called
ADLSE Runwill track these as normal execution logs.