-
Notifications
You must be signed in to change notification settings - Fork 43
Introduce multikey indexes #769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I did nothing about "conflict occurs when the sets of extracted keys have a non-empty logical intersection" because I didn't know what that means, and I did nothing about "each key is assigned a logical sequence number" because I couldn't see how that affects an application. I did use the name 'multikey' in an example but not in text because I don't suppose there's a desire to get this confused with another vendor's multikeys, which aren't closely similar. |
Hi! I am not shure that this is correct:
In fact, when not-nullabale part defines some path with multikey index placeholder, all referenced documents must contain corresponding leaf; otherwise the error is raised. I mean:
As you see, James is inserted in 'phone_type' index twice: by 'home' key and by an empty key. Finally, index store only the last key occurrence/tuple:
|
Uh oh!
There was an error while loading. Please reload this page.
Any JSON index in which at least one partition contains "[*]" (array index placeholder) sign is called a "Multikey". Such indexes allow you to automatically index set of documents sharing the same document structure.
Multikey indexes design have a number of restrictions which must
be taken into account:
Example 1:
Example 2:
Requested by @kshcherbatov in tarantool/tarantool@f1d9f25.
The text was updated successfully, but these errors were encountered: