-
Notifications
You must be signed in to change notification settings - Fork 368
Update tables.md #7652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Update tables.md #7652
Conversation
src/unify/profiles-sync/tables.md
Outdated
Raw tables contain complete historical data when using historical backfill. | ||
Raw tables contain complete historical data when using historical backfill. | ||
|
||
Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not refer to the actual change history. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we do not want to set to the current timestamp also? Also what is this timestamp? What does it refer to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
timestamp
refers to the instant at which the event was ingested into Segment. For backfill, we don't refer to individual events, but to the final profile state. So we don't have access to the original event timestamps.
Proposed changes
Adding note on
Timestamp
column being null in Profiles tables in case of backfill. This is expected behaviour and happens because we infer historical profile changes from the current state of the profile.Verified that
Timestamp
is null by running backfill in Staging.More context: Slack thread.
CSE requested change in documentation here: JIRA.
Merge timing
ASAP once approved.
Related issues (optional)
JIRA ticket: link.