I will add that I think big-endian support would be valuable so that the library can be used everywhere, including more exotic mainframe type systems like IBM Z.
That said, the code review burden to other C++ developers is likely to become significant, so a solo developer with access to big-endian hardware submitting pull requests could be problematic since no one else with close knowledge of the codebase has a need to support big-endian. That said, if big-endian developers would assist with other parts of the C++ project as a sort of "quid-pro-quo" to balance the time spent on code review relating to big-endian that would be helpful. On Mon, Apr 20, 2020 at 12:38 PM Antoine Pitrou <anto...@python.org> wrote: > > > Hello, > > Recently some issues have been opened for big-endian support (i.e. > support for big-endian *hosts*), and a couple patches submitted, thanks > to Kazuaki Ishizaki. See e.g.: > > https://issues.apache.org/jira/browse/ARROW-8457 > https://issues.apache.org/jira/browse/ARROW-8467 > https://issues.apache.org/jira/browse/ARROW-8486 > https://issues.apache.org/jira/browse/ARROW-8506 > https://issues.apache.org/jira/browse/PARQUET-1845 > > Achieving big-endian support support accross the C++ Arrow and Parquet > codebases is likely to be a very significant effort, potentially > requiring cooperation between multiple developers. An additional > problem is that, without any Continuous Integration set up, it will be > impossible to ensure progress and be notified of regressions. > > If other people are seriously interested in the desired outcome, they > should probably team up with Kazuaki Ishizaki and discuss a practical > plan to avoid drowning in the difficulties. > > Regards > > Antoine.
