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) --
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
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
3 matches
Mail list logo