Closed ikwattro closed 8 years ago
I'm not sure if this is a bug in Neo4j, but it definitely seems to be a change in behaviour. I'll write a test case and report it. In the meantime, the dirty workaround is to set the batchSize
in AllNodesWithLabel
to Integer.MAX_VALUE
:(
Ha I will test. Thanks for checking.
On 25 November 2015 at 11:02, Michal Bachman notifications@github.com wrote:
I'm not sure if this is a bug in Neo4j, but it definitely seems to be a change in behaviour. I'll write a test case and report it. In the meantime, the dirty workaround is to set the batchSize in AllNodesWithLabel to Integer.MAX_VALUE :(
— Reply to this email directly or view it on GitHub https://github.com/graphaware/neo4j-framework/issues/37#issuecomment-159557299 .
Christophe Willemsen | Graph Aware Limited
Phone: +44 (0) 333 444 7274 | Mobile: +32 (0) 489 687 208 christophe@graphaware.com | @graph_aware | www.graphaware.com
@bachmanm Not sure if it is related to the framework or through neo4j/lucene
_Scenario : _
Using
IterableBatchTransactionExecutor
to add labels toAllNodesWithLabel
.Failing test :
Test available in a dedicated branch : https://github.com/graphaware/neo4j-framework/blob/labels-ibtx/tx-executor/src/test/java/com/graphaware/tx/executor/batch/IterableInputAddingLabelsTest.java
Note that with 2k, 20k, or 200k nodes it doesn't throw the error.
Throwing :