-
Notifications
You must be signed in to change notification settings - Fork 371
Note added on Timestamp column being null during backfill #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
Merged
Merged
Changes from 7 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
889591b
Update tables.md
ksaha873 a6972d2
Update tables.md
ksaha873 8884c75
Update tables.md
ksaha873 307d5fc
Update tables.md
ksaha873 6e7f1bc
Update tables.md
ksaha873 e2d6a54
Update tables.md
ksaha873 20f63b7
Update tables.md
ksaha873 ae95ff5
Update tables.md
ksaha873 8e8f01c
Update tables.md
ksaha873 f31b8c6
Update src/unify/profiles-sync/tables.md
ksaha873 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -105,7 +105,9 @@ Profile raw tables contain records of changes to your Segment profiles and Ident | |
|
||
With raw tables, you have full control over the materialization of Profiles in your warehouse, as well as increased observibility. | ||
|
||
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. | ||
|
||
### The id_graph_updates table | ||
|
||
|
@@ -296,7 +298,7 @@ If you're not using materialized views for Profile Sync and would like to switch | |
2. **Request a Full Profiles and Events Backfill** | ||
- After enabling the materialized views, you'll need to ensure historical data is populated in the materialized tables. | ||
- Write to [[email protected]](mailto:[email protected]) and request: | ||
- A full **Profiles Backfill** to populate historical profiles data. | ||
- A full **Profiles Backfill** to populate historical profiles data. Materialized views will have null `Timestamp` for the same reason as in Profile events table, discussed above. | ||
- An **Events Backfill** to include any relevant historical events, including a date range for Segment to pull data in for the events backfill. | ||
|
||
3. **Verify Your Data** | ||
|
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.
Uh oh!
There was an error while loading. Please reload this page.