arrow datastore: read+write query path MVP#428
Conversation
|
Unsurprisingly, actually thoroughly testing the thing surfaced a million critical bugs 🙄: added tests and fixes for all of those. Still need to add the benchmark suite before calling it a complete skeleton, but already I feel much more confident undrafting this. |
…oesn't really make sense anymore
434741f to
f424684
Compare
|
emilk
left a comment
There was a problem hiding this comment.
Amazing work 👏👏👏
I found some room for improvement though 😆
| /// entity: this/that | ||
| /// buckets: [ | ||
| /// IndexBucket { | ||
| /// time range: from -∞ (inclusive) to +9223372036.855s (exlusive) |
There was a problem hiding this comment.
this doesn't look like an accurate time range, given the data below
There was a problem hiding this comment.
I purposely want it to look wrong though: this PR completely ignores bucketing and as such it doesn't pretend to get anything right about it.
|
Alright, that should hopefully cover it all @emilk! Well, apart from the bucketing stuff; but as I said above, that's the subject of the next 2 PRs, on which I will jump ASAP :) |
An MVP implementation of an Arrow-based datastore that closely follows the design that we've been mulling over the past few weeks.
This is entirely dynamic: insert anything you want, retrieve anything you want!
Consider this step 1 of the usual "1) make it work 2) make it correct 3) make it fast".