Skip to content
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.

migrations #147

Closed
dimiandre opened this issue Feb 21, 2024 · 2 comments
Closed

migrations #147

dimiandre opened this issue Feb 21, 2024 · 2 comments

Comments

@dimiandre
Copy link
Contributor

We need a way to migrate tables and update old blocks data, otherwise every time there is a structure change we need to resync the indexer

@rllola
Copy link
Contributor

rllola commented Feb 28, 2024

Hi!

It is a good point. After merging this PR migrations would be not needed for the most part. It will store decoded data in JSON and not in tables anymore.

The only time we would need migrations would be for change in the more meta part of the protocol which we don't expect to change. Also because we expect a lot of data and those data are available, we would prefer re-syncing over migration. It is faster because when syncing we don't have indexes created yet and the data can be extracted from a node so dropping a table doesn't mean they are lost. I also suspect migration over index data to be slower than actually starting from scratch so you don't get anything from this. Of course this could evolve but for now it is not needed.

@rllola rllola closed this as completed Feb 28, 2024
@opsecx
Copy link
Contributor

opsecx commented Mar 10, 2024

We need a way to migrate tables and update old blocks data, otherwise every time there is a structure change we need to resync the indexer

Agree, was discussing this with Lola in discord the other day. Creating a new issue re some of this, may be of help to you too eventually.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants