-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
chore!: skip addDenomReverseIndex in bank v3 migration #19266
chore!: skip addDenomReverseIndex in bank v3 migration #19266
Conversation
Hey folks, I checked this and it looks like it will break |
Hey, I appreciate the input! Could you elaborate a bit more? I did not understand this part:
I don't understand what you mean by That EDIT: |
The query would return incomplete and misleading data since the underlying index that powers it was not populated during migration due to being prohibitively resource and time intensive on cosmoshub-4. Writing to the underlying index was also disabled, except in the case of calls to initBalances (only happens on genesis/restart). It is recommended that an external indexer is used for querying this data.
418bb4a
to
e39021d
Compare
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.
LGTM
Description
This PR skips running
addDenomReverseIndex
inbank/v3
migration.This operation was prohibitively expensive to run on the Cosmos Hub (required 128GB RAM) and took 5h to complete.
After consulting with the cosmos-sdk core team, it was deemed this migration is safe to skip as whitnessed by changes on osmosis' fork:
The
DenomOwners
query that used the underlying index was disabled to avoid returning incomplete information (since the index would not contain all denom owners but only those who with recent transfers):DenomOwners
query and stop populating the reverse index)Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
in the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...