Remove incorrect info about customer keys from docs site #277
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
See here: https://amperity.slack.com/archives/C029LR4U3CH/p1736289805370659?thread_ts=1736285414.875279&cid=C029LR4U3CH - Me: CKs also link records if you’ve got transitive FK matches per this from the docs site: - Docs: There may be multiple customer keys per Amperity ID. This is because customer keys may also be tagged as foreign keys. - Joe: To my read, that’s wrong. This may be referring to interaction tables that get linked via FKs but that happens outside of stitch and those linked records won’t show up in unified_coalesced.
Greenninja4
requested review from
jamescott and
Jacksonbaker323
as code owners
piperwolf
approved these changes
Jan 7, 2025
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.
Removes some incorrect info about customer keys from docs site. See here