-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update the collisions Readme with the new replicator details #889
Conversation
Need to update with some new DAG details from #902 |
@gabrielwol Can you update the doc with the new DAG stuff? |
2. The `collisions_replicator.collision_no` materialized view, which creates a unique id (UID) for each collision, is refreshed. | ||
3. The `collisions_replicator.events` and `collisions_replicator.involved` materialized views are refreshed (more on this below). | ||
4. New records, deletions and updates to existing records are tracked in a table called `collisions_replicator.logged_actions`. | ||
### Updating Existing Tables | ||
|
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.
nice mention of the dependencies function :P
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.
That was Islam actually 🥲
New no_backfill task
@gabrielwol I made a few small edits and changed some links. LGTM. Please merge + close as appropriate! |
Thanks for the edits Maddy! |
What this pull request accomplishes:
move_staging
tocollisions
Closes issue #933