tustvold opened a new issue, #2871: URL: https://github.com/apache/arrow-rs/issues/2871
**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*) --> `lexsort`, `lexsort_to_indices`, `lexicographical_partition_ranges`, etc... make use of `LexicographicalComparator` to compare rows. The branching and dynamic dispatch involved in this comparator is relatively expensive. Converting to the row format first, and comparing these rows has been found to offer significant performance advantages in similar applications - https://github.com/apache/arrow-datafusion/pull/3386. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> We should provide examples, and potentially some utilities if necessary, to use the row format for these use-cases instead. We can then deprecate the lexicographic kernels and eventually remove them **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> We could leverage the row format within the existing kernels, however, this has a few drawbacks: * The additional memory consumption is not necessarily obvious * When chaining operators together, e.g. sort then partition, the row format conversion will be performed twice * It isn't obvious how process data in batches **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]
