-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dbnode] Integrate arrow iterators into tile aggregation #2477
[dbnode] Integrate arrow iterators into tile aggregation #2477
Conversation
Codecov Report
@@ Coverage Diff @@
## linasm/aggregate-tiles-plus-arrow-iterators #2477 +/- ##
==============================================================================
- Coverage 71.5% 63.6% -7.9%
==============================================================================
Files 1066 319 -747
Lines 94340 29920 -64420
==============================================================================
- Hits 67512 19058 -48454
+ Misses 22286 9360 -12926
+ Partials 4542 1502 -3040
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
…com:m3db/m3 into linasm/aggregate-tiles-plus-arrow-iterators
… into linasm/integrate-arrow-iterators
…m/integrate-arrow-iterators
…e file on open (#2468) * Add schema.VersionChecker VersionChecker allows us to make decisions around how to proceed depending on the Major and Minor Version in the index info file. * Add DecoderStreamWithDigest * Wire up index entry checksum validation on decode
Also removed concurrency from tile iterators and cleaned up utility
…-cross-block-series-reader
…ock-series-reader
…-cross-block-series-reader
…-cross-block-series-reader
…-cross-block-series-reader
…/integrate-arrow-iterators
Superseded by #2543 |
What this PR does / why we need it:
Uses arrow iterators for large tile aggregation.
Special notes for your reviewer:
This is relative to a branch with #2466 and #2451 merged in.
Does this PR introduce a user-facing and/or backwards incompatible change?:
Does this PR require updating code package or user-facing documentation?: