Skip to content
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

Allow pindexer to handle schema changes itself #5125

Open
cronokirby opened this issue Mar 10, 2025 · 0 comments
Open

Allow pindexer to handle schema changes itself #5125

cronokirby opened this issue Mar 10, 2025 · 0 comments
Assignees
Labels
A-indexing Area: Relates to event indexing.

Comments

@cronokirby
Copy link
Contributor

Right now, when the pindexer schema changes, one needs to know about this inherently, manually wipe the entire database, and then reindex everything from scratch.

Wiping everything is often unnecessary, especially if a minor change in one schema causes other app views to need to be reindexed, unnecessarily, as well.

Having to manually keep track of whether schema changes happened is also error prone.

Solution

App views should know what schema version they have, and we should record it in the state we keep track of for each app view. App views should also know how to reset themselves, so that when we detect that that version doesn't match what we currently have, the app view can safely delete all of the tables it might have created in the past.

@cronokirby cronokirby added the A-indexing Area: Relates to event indexing. label Mar 10, 2025
@cronokirby cronokirby self-assigned this Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-indexing Area: Relates to event indexing.
Projects
None yet
Development

No branches or pull requests

1 participant