tustvold opened a new issue, #2296: URL: https://github.com/apache/arrow-rs/issues/2296
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) --> All `Array` implementations must implement the `JsonEqual` trait. However: - UnionArray will always panic - DictionaryArray is incorrect (#2294) - It is unclear to me why we would special case JSON - It complicates making JSON an optional feature **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> Rather than maintaining parallel logic to interpret `serde_json::Value` as arrow arrays, I wonder if we can just remove the `JsonEqual` functionality and encourage conversion to arrow arrays. I'm unclear of a use-case that would require highly-performant comparison of arrow and JSON data **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> **Additional context** <!-- Add any other context or screenshots about the feature request here. --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
