Update materialised tables #7334
Open
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
pwseg
reviewed
Feb 13, 2025
| @@ -266,6 +266,9 @@ With Profiles Sync, you can access the following three tables that Segment mater | |||
|
|
|||
| These materialized tables provide a snapshot of your Segment profiles, batch updated according to your sync schedule. | |||
|
|
|||
| > success "" | |||
| > Materialised view tables will have two months of historical data on backfill. | |||
|
|
|||
There was a problem hiding this comment.
@vanand17 Can you clarify what this means?
Does it mean that we only store two months of data at any time? So if a user checks the table today, they'll only see data going back 60 days, and no further?
Or does it mean that the backfill process only retrieves two months of historical data when it first runs? In other words, if someone sets up Profiles Sync today, the system would pull in the last 60 days of data, and from that point forward, it would keep accumulating new data.
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.
Proposed changes
Currently, it is not clear what amount of historical data is available in materialised tables in our public docs
Merge timing
Related issues (optional)
NA