Hi, I was considering mvstore for time series data on a mobile device. - My usage would be high frequency writes (sensor data) and large batch reads of ranges. - The schema would be key=timestamp, value=data from multiple sensors
What is unclear in my mind, is whether I should attempt the R-Tree implementation with dimensionality = 1, or use another implementation. More specifically: - For range queries on a key representing timestamp, is one implementation better - For concurrent writes, is one implementation better. My confusion stems from ambiguity in the online documentation section(s) "R-Tree and Pluggable Map Implementations" "In addition to the default MVMap (multi-version map), there is a map that supports concurrent write operations, and a multi-version R-tree map implementation for spatial operations." This implies one implementation allows concurrent writes and the other don't. However the next section "Concurrent Operations and Caching" says, without qualification: "Concurrent reads and writes are supported." Any other tips on storing time series would be greatly appreciated, Thanks -Alex -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
