Hi Todd,
The sample code creates nodes and relationships by parsing 4 csv files.
Thank you for trying to trigger this behaviour with this sample.
Núria
2009/12/9 Mattias Persson matt...@neotechnology.com
Could you provide me with some sample code which can trigger this
behaviour with the
Hi again, Núria (it was I, Mattias who asked for the sample code).
Well... the fact that you parse 4 csv files doesn't really help me
setup a test for this... I mean how can I know that my test will be
similar to yours? Would it be ok to attach your code/csv files as
well?
/ Mattias
2009/12/9
Hi Mattias,
In my last e-mail I have attached the sample code, haven't you received it?
I will try to attach it again.
Núria.
2009/12/9 Mattias Persson matt...@neotechnology.com
Hi again, Núria (it was I, Mattias who asked for the sample code).
Well... the fact that you parse 4 csv files
Oh ok, It could be our attachments filter / security or something...
could you try to mail them to me directly at matt...@neotechnology.com
?
2009/12/9 Núria Trench nuriatre...@gmail.com:
Hi Mattias,
In my last e-mail I have attached the sample code, haven't you received it?
I will try to
Hi Mattias,
I have already done it 10 minutes ago. If you need an example to see the
format of the 4 csv files, I can send it to you.
Thanks again,
Núria.
2009/12/9 Mattias Persson matt...@neotechnology.com
Oh ok, It could be our attachments filter / security or something...
could you try to
Associating nodes with a type node is a good approach, especially if you
want to be able to do queries like give me all nodes of type X. But for
knowing the semantic type of a node when found through a general traversal I
prefer to use the navigational context of the node. For example if I have a
Hi, Tobias.
Thanks for your thoughts and ideas.
My requirement is not only to know the type of something, but also to
store metadata for types so that I can catalog the property type of
each individual property in a node for a given type. It's a bit
complicated, but we are
I see. I realized that this was what you were after. What I was proposing
was that you would know the types for the properties given the type of the
node. The types for the nodes in your case would be more abstract, perhaps
just defined by the set of properties. I used concrete types in my
Hi, all.
Here are a few questions and comments that I'd welcome feedback on :
Questions:
- If you delete the reference node (id = 0), how can you recreate
it?
- If you have a number of loose or disjoint graphs structured as
trees with a single root node, is there a
Hi, all.
When trying to load a few hundred thousand nodes relationships (chunking
it in groups of 1000 nodes or so), we are getting an out of memory heap
error after 15-20 minutes or so. No big deal, we expanded the heap settings
for the JVM. But then we also noticed that the
FYI, we experimented with different heap size (1GB), along with different
chunk sizes, and were able to eliminate the heap error and get about a 10X
improvement in insert speed. It would be helpful to better understand the
interactions of the various Neo startup parameters, transaction buffers,
When doing some large traversal testing (no writes/updates), I noticed that
the neostore.propertystore.db.strings file was seeing a lot of read I/O (as
expected) but also a huge amount of write I/O (almost 5X the read I/O rate).
Out of curiosity, what is the write activity that needs to occur when
12 matches
Mail list logo
