-
Notifications
You must be signed in to change notification settings - Fork 786
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
Remove JsonEqual
trait
#2296
Comments
This appears to be part of the integration test plumbing, which makes its inclusion in the public API even more unusual? FYI @viirya |
I think in the integration test, JSON data is read and converted to arrow array before comparing? Does it compare JSON with arrow arrays directly? |
It at least appears to be using the JsonEqual functionality, but I'm not very familiar with this part of the codebase |
Oh, I will check it. I might miss it now. |
At second glance, JsonEqual functionality is used by Although the stuffs like Currently seems the JsonEqual functionality is only used in some IPC tests where JSON files are read and compare with arrow arrays without converting. For that tests, I think we can follow integration test to convert JSON to arrow arrays before comparing. I can take some time on this. |
As another data point, in our integration tests we convert result RecordBatches to json to compare against the expected results. So removing the JsonEqual support should be fine. |
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
All
Array
implementations must implement theJsonEqual
trait. However:Describe the solution you'd like
Rather than maintaining parallel logic to interpret
serde_json::Value
as arrow arrays, I wonder if we can just remove theJsonEqual
functionality and encourage conversion to arrow arrays. I'm unclear of a use-case that would require highly-performant comparison of arrow and JSON dataDescribe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: