Use obf_id to create IDs
#58
Open
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.
These PRs should be merged before the one I'm opening here: #44 , #50 , #53, #56 , #57 . The PR being opened here was built on top of those PRs in an attempt to avoid lots of merge conflicts (especially with #56). This PR can be reviewed by checking 440e955.
This PR makes use of the obfuscation function introduced in #50. It replaces instances of
FARM_FINGERPRINT(GENERATE_UUID())which created 64 bit integers that could be negative and varied from build to build. The goals of this new approach are to:obf_idfunctionThe approach for identifying a deterministic source was to step through these options until a unique source was identified:
trace_id, which is generally uniquetrace_idwas not unique, combine it with another variable to make the combination uniqueThe instances of
FARM_FINGERPRINT(GENERATE_UUID())which setload_row_idwere not updated as this column falls outside of the official CDM table columns.