Hi Chris, yes they are still stored as such. What do your properties look like? How many do you have? How many do you access when querying and which types?
Can you explain more details about your aggregating queries? You could add some more intermediate structures to access your data, more quickly, like a tree that keeps some data pre-calculated, see Rik's blog for an example: http://blog.bruggen.com/2014/03/using-neo4j-to-manage-and-calculate.html On Sun, Jul 27, 2014 at 7:02 AM, Chris Wj <[email protected]> wrote: > Hello, I have a question concerning Neo4j property accessing. Are node > properties and edge properties still stored as linked lists in 2.0? I am > trying to figure out if querying for nodes with given properties will have > poor performance because it would have to traverse the entire property list. > > While my data is best represented by a graph, there are some aggregation > queries that I would like to perform on the data. To do so, I have to group > the data by certain properties and then use other property values to > perform the aggregation. > > How can I make accessing properties themselves fast? > > -Chris > > -- > 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. > -- 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.
