I've been working with OrientDB for a while, and have come across some potential index problems, which might be bugs, but I am not sure, so I thought I would check here first.
A detailed explanation of the index issues are on the following Gist:
- Problem 1: The less optimum index from the base class is used instead of the more optimum index on the inherited class, making it inefficient with many records.
- Problem 2: The index used in the query is chosen based on the order in which it was created. In addition, it does not use multiple indexes to satisfy the query, making it inefficient with many records.
- Problem 3: Using a fulltext index at the same time as another index does not work. Therefore you must use subqueries to limit the result, which is very inefficient when there are many records.
Looking forward to hearing anyone's thoughts