You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create the index : curl -X POST 'http://localhost:7700/indexes' --data '{"uid": "test", "primaryKey": "docid"}' curl -X POST 'http://localhost:7700/indexes/test/settings' --data '{"filterableAttributes": ["label"]}'
Attempt to delete any document: curl -X DELETE 'http://localhost:7700/indexes/test/documents/1_4'
Check the status, see it failed: curl -X GET 'http://localhost:7700/indexes/test/updates'
Expected behavior
I expect it not to fail.
MeiliSearch version: v0.21.0rc6
Works fine with v0.20.0
Additional context
If you skip modifying the filterableAttributes index settings, then it works ok. So it must have something to do with that.
Note, if you change it to "filterableAttributes": ["doc_id"] it still fails with the same internal: decoding failed error
The text was updated successfully, but these errors were encountered:
Hello @Sembiance! Thank you so much for this report and for the detailed steps! 🙏 I think this is the same bug as #1594 we did not succeed to reproduce!
I followed your steps and I got the same error as you report!
We'll fix this for v0.21.0
curquiza
changed the title
'internal: decoding failed' error upon deleting documents in v0.21.0rc6
Decoding failure when deleting documents
Aug 20, 2021
317: Fix the facet string docids filterable deletion bug r=Kerollmops a=Kerollmops
Fixes a bug where the deletion of documents was returning a decoding error. But only when the settings are set with filterable attributes.
This bug was introduced in #254 in which we made the engine faster in returning the facet distribution. We changed the way we were storing the inverted index, we were no more storing only documents ids with the original values but also groups identified with integers, depending on the facet level we were using. This is similar to how facet numbers are already stored.
⚠️ As `@curquiza` already said, we must first revert #309 before merging this!
Related to meilisearch/meilisearch#1601.
Co-authored-by: Clément Renault <clement@meilisearch.com>
Describe the bug
Attempting to delete any document from a dataset below results in an error:
To Reproduce
meilisearch
v0.21.0rc6
curl -X POST 'http://localhost:7700/indexes' --data '{"uid": "test", "primaryKey": "docid"}'
curl -X POST 'http://localhost:7700/indexes/test/settings' --data '{"filterableAttributes": ["label"]}'
any
document:curl -X DELETE 'http://localhost:7700/indexes/test/documents/1_4'
curl -X GET 'http://localhost:7700/indexes/test/updates'
Expected behavior
I expect it not to fail.
MeiliSearch version: v0.21.0rc6
Works fine with v0.20.0
Additional context
If you skip modifying the
filterableAttributes
index settings, then it works ok. So it must have something to do with that.Note, if you change it to
"filterableAttributes": ["doc_id"]
it still fails with the sameinternal: decoding failed
errorThe text was updated successfully, but these errors were encountered: