Inconsistent Order by createdAt_ASC

[preschian]

Hi, I just found out that there are some issues with ordering with our query.

1. Is there a way to get consistent order to our query?
2. Can the query be told to purge some specific ID?

claim 10 drops	trigger update metadata
id,name,blockNumber 379-2404223588,MEADOW,6750520 379-2404238914,MEADOW,6750520 379-2404144915,MEADOW #150,6750520 379-2404257488,MEADOW #151,6750520 379-2404267204,MEADOW #152,6750520 379-2404270139,MEADOW #155,6750520 379-2404285152,MEADOW #147,6750520 379-2404387843,MEADOW #149,6750520 379-2404624504,MEADOW #153,6750520 379-2404630981,MEADOW #148,6750520	id,name,blockNumber 379-2404144915,MEADOW #150,6750520 379-2404257488,MEADOW #151,6750520 379-2404270139,MEADOW #155,6750520 379-2404285152,MEADOW #147,6750520 379-2404387843,MEADOW #149,6750520 379-2404624504,MEADOW #153,6750520 379-2404630981,MEADOW #148,6750520 379-2404223588,MEADOW #147,6750520 379-2404238914,MEADOW #148,6750520 379-2404267204,MEADOW #152,6750520

related: kodadot/nft-gallery#10025

[vikiival]

Can you please expand your thoughts please?

[preschian]

Hi Vik, the order from NFTs with the same block numbers is inconsistent.

while claiming the drops, this id 379-2404223588 is on index 146
then, I test it by updating the metadata for all of them. Then, the order was changed. This id 379-2404223588 was changed to index 147

The expected result is that 379-2404223588 is still on index 146. All of them should be the same before and after

Is there a way to make it consistent? Currently, the order is using "orderBy": ["createdAt_ASC"]

Can the query be told to purge some specific ID?

alternatively, is there a way to purge some data to query?

[vikiival]

Hi Vik, the order from NFTs with the same block numbers is inconsistent.

while claiming the drops, this id 379-2404223588 is on index 146 then, I test it by updating the metadata for all of them. Then, the order was changed. This id 379-2404223588 was changed to index 147

Fixed for you in 44c9650

Can the query be told to purge some specific ID?
alternatively, is there a way to purge some data to query?

Still dont understand, sorry

[vikiival]

Made update in #268, it should be much faster

[preschian]

Still dont understand, sorry

something like hit our query endpoint (mutation graphql), then the query will reindex the item again

Made update in #268, it should be much faster

thank you

[vikiival]

something like hit our query endpoint (mutation graphql), then the query will reindex the item again

Well, I can do that either manually or reindex

Since I made #268 I need to make deploy anyway

[preschian]

any idea why indexer return wrong metadata. I'm trying to update metadata on ahk: https://assethub-kusama.subscan.io/extrinsic/6751672-2

the metadata return #153: https://fxart-beta.kodadot.workers.dev/metadata/v1/json?chain=ahk&collection=379&nft=2404285152&metadata=ipfs:%2F%2Fbafybeihutexevnef7j4msobm5v5uczx2mempxeixihnbgrmpwqogzcbtzm%2F0.json

but, on indexer always return #147: https://kodadot.xyz/ahk/gallery/379-2404285152

Well, I can do that either manually or reindex

oohh, I mean reindex but just for specific item only, not reindex all from the starts

[vikiival]

oohh, I mean reindex but just for specific item only, not reindex all from the starts

• Stick v11 #270
• Speck v12 #271