I was curious to know if multiple indexes in Sql querie where clause are supported now in OrientDB 3.0 above, I tried to see on my own but the explain format seems to have changed now, it no longer shows the involved indexes field.
Thanks in advance.
OrientDB supports multiple indexes for OR conditions and for class hierarchies, but not for AND conditions
Thanks for your response. When i tried to check this behaviour in 3.0, it seems to be atleast creating a execution plan that involves multiple search field indexes now, as compared to the prev execution which wasnt well with chosing best index and would use only one index and no search fields.
Yes, the execution planner in v 3.0 is much smarter, and the resulting execution plan is much easier to understand
Thanks for your answer. And I also have a question here: is multiple field lookup in transformer JSON supported? I create a index with multiple property, and don’t know how to use it in the ETL process.