Changed gl_journal_entries replication key#56
Merged
leslievandemark merged 3 commits intoNov 3, 2021
Merged
Conversation
Contributor
|
Hi @DownstreamDataTeam, thanks for your contribution! In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. |
|
This looks great we have the exact same issue! |
leslievandemark
approved these changes
Nov 3, 2021
Merged
|
You did it @DownstreamDataTeam! Thank you for signing the Singer Contribution License Agreement. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of change
Changed
replication_keysandbookmark_fieldfor gl_journal_entries stream frombooking_datetocreation_date.The problem that this change solves is that, currently, we are missing journal entries records when transactions are reversed.
A test that was performed (without code changes):
start_dateto current dateThe expected result: at least the reversed transaction records.
The actual result: didn't get the records for the reversed transaction.
After the change from
booking_datetocreation_date, the reversed transactions were synced.Here are some json snippets (
"start_date": "2021-10-18T00:00:00.000000Z"):Result before code changes
Result after code changes
Rollback steps