-
Notifications
You must be signed in to change notification settings - Fork 39
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
feat: Add dictionary support in integration test utility #342
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #342 +/- ##
==========================================
+ Coverage 87.96% 88.12% +0.15%
==========================================
Files 72 72
Lines 11733 11913 +180
==========================================
+ Hits 10321 10498 +177
- Misses 1412 1415 +3 ☔ View full report in Codecov by Sentry. |
I tried just running the new tests via archery and had a few more failures than I expected based on your disclaimer about known unsupported types. Specifically Full archery output
Does the above look correct to you? And, as a side note, I ran into some trouble setting up archery correctly for the integration tests. I tried installing archery with just the |
Thank you for running the tests!
You're right that I didn't mention the stringview/binary view...nanoarrow doesn't have support for those, either yet. I don't see any output there I didn't expect.
I had no idea that the |
If there are no objections, I'll merge this tomorrow morning and continue with the rest of the integration test implementation! |
fd25c39
to
49ce3d4
Compare
This PR implements dictionary support in the integration test utility and fixes a few problems identified with integration testing to ensure that it actually works end-to-end (via apache/arrow#39302 ). The changes are:
std::unordered_map<>
with aUniqueSchema
and a few const overloads were missing)It can now be tested with
archery
(after checking out apache/arrow#39302 ):The current failures are limited to the remaining unimplemented types (datetime types and decimal).
And for future me or anybody who has to/wants to launch a debugger with a segfaulting integration test in VSCode, it can be done with this launch.json: