[Neo4j] Re: Newby: Modelling best practices

2014-08-14 Thread Kenny. Bastani
Option 5 is the recommended best practice for this use case. On Sunday, August 10, 2014 3:56:04 PM UTC-7, Tan-Minh Truong wrote: > > Hello all, just got started on Neo4J and I was wondering if there were > best practices with regards to using Labels versus Relationships versus > Properties when

[Neo4j] batch import 2.0 > avoiding duplicate relationships?

2014-08-14 Thread gg4u
Hi, a quick note on the batch importer: does it import the relationships with an equivalent *create ()-[]->() *or *merge ()-[]-()* ? In order to reduce the size of the graph, I would like to avoid to have duplicate relationships, in the sense that if a rel a-[]-b exist, that is equivalent t

[Neo4j] batch import 2.0 > failed automatic indexing?

2014-08-14 Thread gg4u
Hello folks! I've done a batch import of 4M nodes and 100M rels. I set up autoindexes before import, but something got wrong apparently: it takes ages for querying a single node like: match (n:Users)-[r:REL]-() where n.id = 25 Please help me to understand if I am doing the following steps corr

[Neo4j] Re: batch importer > failed in importing relationships

2014-08-14 Thread gg4u
Hello! I found the error for failing import of relationships: in the header of relationships should have been specified a keyword used for automatic indexing, like: #node.csv id:int:KEYWORD # rels.csv id:int:KEYWORD id:int:KEYWORD and than in batch properties: batch_import.node_index.KEYWORD=e

[Neo4j] Re: TransactionNotPresentOnMasterException error when executing writes on slave instance

2014-08-14 Thread Erk
Anyone have thoughts on this? Any help would be greatly appreciated. On Tuesday, August 12, 2014 8:27:06 AM UTC-7, Erk wrote: > > I have neo4j 1.9.7 running with 3 instances (2 embedded, and one > standalone). > > Lately we've been seeing the following exception when writes are executed > again

[Neo4j] Re: [SDN 3.1.2] / Random success of a relationship update

2014-08-14 Thread Michael Azerhad
Wow, I succeeded but with the strangest way I could do: Basically, I hadn't had the log: concernedUser.friends.clear() // to be sure that the list is fully updated if was not empty (although not fetched) concernedUser.friends.addAll(concernedUserFriends) //populating the friends list userR