I have tried to profile a query like " profile match (n) where id(n) in [0, 1] return n". No matter whatever the size of the list, the estimation for the number of rows is 25. This is ridiculous. The estimation should be a number based on size of the list.
When I try another way of writing the query: " profile match (n) where id(n) = 0 or id(n) = 1 return n", the estimation can vary according to how many ids the query requires. So I think the optimizer should be fixed for the first case "[id1, id2, id3, ...]". -- You received this message because you are subscribed to the Google Groups "Neo4j" 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.
