The lack of OR or IN index lookups are a pain for me as well. Looking forward to that one--hope it comes in a 2.0.x release rather than a 2.1 release. :)
Happy new year! Wes On Tue, Dec 31, 2013 at 9:41 AM, Debajyoti Roy <[email protected]> wrote: > We are our upgrading our current production system from neo4j 1.9.3 > community to 2.0 community. This supposed to go live in March'14. Just > thought of summarizing and sharing our experience so far in terms of > challenges: > > Cypher features missing: > > 1. No index lookup for IN and OR: > https://github.com/neo4j/neo4j/issues/861 > > · Workaround: core API/traversal > > 2. No like search support: > http://stackoverflow.com/questions/20787666/how-to-use-index-in-neo4j-2-0-for-like-search > > · Workaround: use legacy lucene indexing where needed > > > > Performance: > > 1. Batch committing is slow: > http://stackoverflow.com/questions/20409870/how-to-improve-performance-while-committing-nodes-in-bulk-with-neo4j-2-0-rc1 > > · Workaround: Use pessimistic locks instead of Constraints where > needed. > > 2. Reading data under heavy threading is slow: > http://stackoverflow.com/questions/20750741/how-to-improve-neo4j-2-0-cypher-executionresult-performance-under-heavy-load > > · *No workaround !!* > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
