Hey Peter,
thanks for the hint. I currently chose another way to store time series.
I'll try to use versioned edges like so:
node_a --- edge_a (t1) --> node_b
If there is an update operation on node b at time t2, a copy of b will
be created and referenced like so:
node_a -- edge_a(t1) --> node_b
node_a -- edge_a (t2) --> node b_new
I will test this model with some benchmarks because there are obviously
some drawbacks. Maybe you can tell me the best way to handle the edges
via Spring Neo4J.
Is there any possiblity to index the edges in Spring or define a sort
order (maybe by timestamp)? I'd like to select the edge_a with "latest
timestamp" at an instance of Node_A. Is something like
...
@RelatedToVia
SortedMap<long, Edge_A>
...
possible?
Currently the implementation would look like this way:
@NodeEntity
class Node_A {
@RelatedToVia
Collection<Edge_A> relations;
// ...
}
@RelationshipEntity
class Edge_A {
@StartNode Node_A from;
@EndNode Node_B to;
long timestamp;
// ...
}
@NodeEntity
class Node_B {
// no need for backward edges
}
Thanks for your help.
Greetings, Martin
Am 21.11.2011 14:19, schrieb Peter Neubauer:
> Martin,
> for storing times, you could try the timeline index in graph
> collections if things are not too long linked, see
> https://github.com/neo4j/graph-collections/blob/master/src/test/java/org/neo4j/collections/timeline/TestTimeline.java
> or some of the other indexes in that component.
>
> Would that help?
>
> Cheers,
>
> /peter neubauer
>
> GTalk: neubauer.peter
> Skype peter.neubauer
> Phone +46 704 106975
> LinkedIn http://www.linkedin.com/in/neubauer
> Twitter http://twitter.com/peterneubauer
>
> http://www.neo4j.org - NOSQL for the Enterprise.
> http://startupbootcamp.org/ - Öresund - Innovation happens HERE.
>
>
>
> On Tue, Nov 15, 2011 at 11:15 AM, s1ck<martin.jungha...@gmx.net> wrote:
>> Hey,
>>
>> I have a very complex domain model which can be perfectly mapped into the
>> neo4j database. OR Mapping is much too complex for the model... The data
>> itself is time series data from multiple sensors which needs to be stored
>> and retrieved (at given timestamps or in given ranges). Are there any good
>> explanations, articles or something else on how to handle this kind of data?
>> The second question is: What's the best way to model a domain in neo4j? I
>> currently use the aproach described in the
>> http://docs.neo4j.org/chunked/milestone/tutorials-java-embedded-entities.html
>> documentation and will also try out the spring graph.
>>
>> Best regards,
>>
>> Martin
>>
>> --
>> View this message in context:
>> http://neo4j-community-discussions.438527.n3.nabble.com/Time-Series-Data-with-complex-domain-model-tp3509252p3509252.html
>> Sent from the Neo4j Community Discussions mailing list archive at Nabble.com.
>> _______________________________________________
>> Neo4j mailing list
>> User@lists.neo4j.org
>> https://lists.neo4j.org/mailman/listinfo/user
>>
> _______________________________________________
> Neo4j mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
