Hi John, you _always_ have to remove and then add things to the index, there is no inherent update involved.
So you might just have a slightly messed up index that contains a ton of additions on top of each other. Try to drop it, fix the addition to remove + add and recreate the index. Michael > Am 20.03.2015 um 03:47 schrieb [email protected]: > > Hi, > > I am using Neo4j version 2.1.7 embedded in my Java application using JRE > 1.8.0_32 > > RelationshipIndex queries with a starting point node seem to work incorrectly > with some data. > > For example if I create nodes 1, 2, 3 and 4 and then create relationships > 1->2, 1->3 and 1->4: > > Node leftNode = createNode("1"); > createAndIndexRelationship(leftNode, createNode("2")); > createAndIndexRelationship(leftNode, createNode("3")); > createAndIndexRelationship(leftNode, createNode("4")); > > This query returns all three relationships: > > relationshipIndex.query(QueryContext.numericRange( > "updateUnixTime", Long.MIN_VALUE, Long.MAX_VALUE)); > > This query returns just the second two of the relationships: > relationshipIndex.query(QueryContext.numericRange( > "updateUnixTime", Long.MIN_VALUE, Long.MAX_VALUE), leftNode, null); > > I confirmed the existence of the nodes and relationships in the Neo4j > webadmin management page. > The first query confirms that the relationship index contains all of the > relationships. > > Sometimes my application works for days without this issue appearing, then it > starts happening again. > Restarting the application does not fix the issue. > > I experimented and learned some seemingly odd but potentially related things: > If I readd the relationship with a new value for updateUnixTime the > relationship does NOT start appearing in the query. > If I remove and then readd the relationship with a new value for > updateUnixTime in a single transaction the relationship does NOT start > appearing in the query. > If I remove and then readd the relationship with a new value for > updateUnixTime in a two separate transactions the relationship DOES start > appearing in the query. > > > I would appreciate if anyone would advise me on potential fixes, workarounds > or ways to further debug this and get to the root cause. > > Thank you, > John > > > > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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.
