This repository has been archived by the owner on Sep 6, 2023. It is now read-only.
Multi company parallel exports session queue #50
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
DuttaSoumya
added a commit
that referenced
this pull request
Oct 12, 2022
* Intermmediate changes * second draft * Adding SessionID as a secondary key on the session table * Working for simultaneous exports * Code Cop * Remove obsolete tags * Documentation * More documentation * improve picture * more fixes * Multi company parallel exports session queue (#50) * 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> * Elaborated on the usage of Multi- company export * Made the execution logs viewable * broke the comment line for readability * Made the messaging more elaborate * Do export for tables that failed last time, even though the data may not have changed since. * Explain the concept when duplicate data has been exported * Fix for entity JSONs not being written during export * removing comments Co-authored-by: Soumya Dutta <soudutta@microsoft.com>
HenriSchulte-MS
added a commit
that referenced
this pull request
Nov 2, 2022
Fixes irregularities on the System Audit fields. (1) Very old records do not appear in the lake sometimes because the SystemCreatedAt field is set to null. This field is now artificaly initialized to a date so that it appears in the lake, and (2) The SystemID field may be repeated over different records belonging to different companies in the same table. Thus, the uniqueness contraint has been fixed. * Intermmediate changes * second draft * Adding SessionID as a secondary key on the session table * Working for simultaneous exports * Code Cop * Remove obsolete tags * Documentation * More documentation * improve picture * more fixes * Multi company parallel exports session queue (#50) * 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> * Elaborated on the usage of Multi- company export * Made the execution logs viewable * broke the comment line for readability * Made the messaging more elaborate * Do export for tables that failed last time, even though the data may not have changed since. * Explain the concept when duplicate data has been exported * Fix for entity JSONs not being written during export * Handling the case when SystemCreatedAt is null for records. * Documenting change * Fixing the uniqueness criteria * more readable * Adding Company field to CurrentData as well, doc * beautification of notable change * Added derived column called UniqueRecordKey, Determine if entity is company specific * Moved around expressions to eliminateSelectAllExceptUniqueRecordKeyColumn. Column selection is now done in sink. Does not affect behavior. Co-authored-by: Soumya Dutta <soudutta@microsoft.com> Co-authored-by: Henri Schulte <henri.schulte@microsoft.com>
DuttaSoumya
added a commit
that referenced
this pull request
Nov 18, 2022
* Intermmediate changes * second draft * Adding SessionID as a secondary key on the session table * Working for simultaneous exports * Code Cop * Remove obsolete tags * Documentation * More documentation * improve picture * more fixes * Multi company parallel exports session queue (#50) * 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> * Elaborated on the usage of Multi- company export * Made the execution logs viewable * broke the comment line for readability * Made the messaging more elaborate * Do export for tables that failed last time, even though the data may not have changed since. * Explain the concept when duplicate data has been exported * Fix for entity JSONs not being written during export * Linked to the replica seeker * Fixing App ID * update docs * Compilation warnings Co-authored-by: Soumya Dutta <soudutta@microsoft.com>
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 first version of the pull request still relies on starting up as many table exports as permitted by the operating limits. So if you have a fairly large table set or if you have too many companies being exported at the same time, chances are that not all exports will happen in the same batch. In order to minimize (not eliminate) this issue, there is a provision made that starts up exports for those tables that were not activated because of the op limits.