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
This should save around 50% of the storage used by the inverted index. We don't need to put min+max namespace IDs in the inverted index, as they don't contribute to collision resistance. To access a key, you can simply truncate the namespace ID.
The text was updated successfully, but these errors were encountered:
Yes it is. This happens in a subtle way. The good thing is that soon the inverted index will be removed altogether with this issue via new protocol: #2971
This should save around 50% of the storage used by the inverted index. We don't need to put min+max namespace IDs in the inverted index, as they don't contribute to collision resistance. To access a key, you can simply truncate the namespace ID.
The text was updated successfully, but these errors were encountered: