You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2020/10/07 06:20:06 UTC

[GitHub] [arrow] kiszk commented on a change in pull request #8374: ARROW-10203: Give guidance on big-endian support in the contributors …

kiszk commented on a change in pull request #8374:
URL: https://github.com/apache/arrow/pull/8374#discussion_r500762410



##########
File path: docs/source/developers/contributing.rst
##########
@@ -304,3 +304,40 @@ to your branch, which they sometimes do to help move a pull request along.
 In addition, the GitHub PR "suggestion" feature can also add commits to
 your branch, so it is possible that your local copy of your branch is missing
 some additions.
+
+Guidance for specific features
+==============================
+
+From time to time the community has discussions on specific types of features
+and improvements that they expect to support.  This section outlines decisions
+that have been made in this regard.
+
+Endianess
++++++++++
+Arrow is primarily a little endian format there has been some effort to
+support big endian platforms as well. Based on a mailing list discussion,
+The requirements for a new platform are:
+
+1. A robut (non-flaky, returns results in a reasonable time) Continuous integration setup.
+2. Performance benchmarks in performance critical parts of the code to demonstrate no
+   regression.
+
+Furthermore for big-endianess support there are two levels that an implementation can support
+1.  Native endianness (all arrow communication happens with processes of the same endianness.
+2.  Cross platform support (implementations will do byte reordering when appropriate for IPC
+    and flight messages).
+

Review comment:
       On some platforms (e.g. C++), there are additional works (e.g. Parquet support in C++) 
   
   Can we create the third level? Or do we put these works into the second level?




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org