In some cases, DipDup can't proceed with indexing without a full wipe. Several reasons trigger reindexing:
|Reindexing triggered manually from callback with
|Applied migration requires reindexing. Check release notes before switching between major DipDup versions to be prepared.
|Reorg message received from TzKT can not be processed.
|One of the index configs has been modified.
|Database schema has been modified. Try to avoid manual schema modifications in favor of 5.7. SQL scripts.
It is possible to configure desirable action on reindexing triggered by a specific reason.
ReindexingRequiredError and quit with error code. The safest option since you can trigger reindexing accidentally, e.g., by a typo in config. Don't forget to set up the correct restart policy when using it with containers.
|Drop the whole database and start indexing from scratch. Be careful with this option!
|Ignore the event and continue indexing as usual. It can lead to unexpected side-effects up to data corruption; make sure you know what you are doing.
To configure actions for each reason, add the following section to the DipDup config: