initcommand. Now you have two conflicting hooks:
on_index_rollback. Follow the guide below to perform the migration.
ConflictingHooksErrorexception will be raised until then.
buffer_sizeoption of a TzKT datasource is set to a non-zero value, and there are enough data messages buffered when a rollback occurs, data is just dropped from the buffer, and indexing continues.
operationones, we can attempt to process a single-level rollback. All operations from rolled back block must be presented in the next one for rollback to succeed. If some operations are missing, the
on_rollbackhook will be called as usual.
on_rollbackhook, which receives
datasource: IndexDatasourceargument and from/to levels. Even if your deployment has thousands of indexes and only a couple of them are affected by rollback, you weren't able to easily find out which ones.
on_rollbackhook is deprecated and superseded by the
on_index_rollbackone. Choose one of the following options:
on_rollbackhook since project creation. Run
initcommand and remove
sql/on_rollbackdirectories in project root. Default action (reindexing) has not changed.
on_rollbackhook and want to leave it as-is for now. You can ignore introduced changes at least till the next major release.
init, move your code to the
on_index_rollbackhook and delete
on_rollbackone. Note, you can access rolled back datasource via
operationindex is overkill for a specific task. An existing alternative is to use a
big_mapindex to process only the diffs of selected big map paths. However, you still need to have a separate index for each contract of interest, which is very resource-consuming. A widespread case is indexing FA1.2/FA2 token contracts. So, this release introduces a new
TokenTransferDataobject is passed to the handler on each operation, containing only information enough to process a token transfer.
config envcommand to generate env-files
-f <filename>option to save output on disk instead of printing to stdout. After you have modified the env-file according to your needs, you can apply it the way which is more convenient to you:
--env-file / -eoption:
X. That way, you can stick to a specific release without the risk of leaving a minor/major update unattended (friends don't let friends use
-pytezosflavor is also available for each tag.