Hey, Thanks for reverting.
Actually i found the problem i was running a query: SELECT FROM weak_link WHERE (in.id = "1" AND out.id = "2") OR (in.id = "2" AND out.id = "1") I indexed the in and out properties of E class. And the vertices connected by Edge (weak_link) also have property (id) indexed. But the above query was not using the indexes and scanning a lot of edges. The time taken by the query was around 2 secs. I used a work around for this: SELECT FROM (SELECT EXPAND(BOTHE(weak_link)) FROM Vertex1 where id="1" ) WHERE in.id="2" or out.id="2" This reduced the time to a few ms. That said, shouldn't the first query use the indexes itself? -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
