Interesting thought... So, "persistence" is a derived from "operations" ? And there is no primary purpose?
Timeseries is for me the effective storage of timestamped values that changes often over time. DBs like Cassandra are optimized to retrieve a slice in time of consequetive data points. On Mon, Jul 13, 2015 at 6:26 PM, Kent Sølvsten <[email protected]> wrote: > I Think i have misunderstood the intention behind timeseries support then. > I was more thinking of timeseries as derived values - the same way that the > indexing May be considered derived from the entity store. And just like in > some architectures the entity may be considered derived from an eventstore. > Den 13/07/2015 15.59 skrev "Niclas Hedhman" <[email protected]>: > > > On Mon, Jul 13, 2015 at 1:58 PM, Paul Merlin <[email protected]> wrote: > > > > > > > > > Any thoughts? > > > > > > I'm all in favor for going towards "Entity=Identity+Value". In the end, > > > this will allow us to drop a bunch of code as EntityState serialization > > > in EntityStores is pretty different than ValueSerialization (was > already > > > before I rewrote ValueSerialization for 2.0). And I don't see the need > > > for theses differences. > > > > > > > Yes, I have also been thinking about that. > > > > Potentially the EntityStore SPI could become somewhat simpler. > > a. "Here is the new Value" per entity, in a two phase process... > > b. EntityStore could throw the whole Value into the timeseries store, > > maybe optimized for cases where a single Property is in the Entity. > > > > My guess is that Indexing/Query might also benefit from such change. > > > > Cheers > > -- > > Niclas Hedhman, Software Developer > > http://zest.apache.org - New Energy for Java > > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
