Skip to content
Discussion options

You must be logged in to vote

An automatic composite index cannot index those arbitrary nested JSON paths directly. OrientDB builds automatic indexes from schema properties of the indexed class; details.uniqueproperites.uniquekey1.value is not a property of Category that the index definition can maintain.

Also note that the values in the sample are one level deeper than the paths in the question: the actual paths end in .value (and there is a double .. before uniquekey2 in the question).

The reliable design is to materialize the values that define uniqueness as schema properties on Category and index those:

CREATE PROPERTY Category.category STRING;
CREATE PROPERTY Category.uniqueKey1 STRING;
CREATE PROPERTY Category.u…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@attururosireddy
Comment options

Answer selected by tglman
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants