You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by "Julien Le Dem (JIRA)" <ji...@apache.org> on 2016/08/10 19:22:20 UTC

[jira] [Created] (ARROW-252) Add implementation guidelines to the documentation

Julien Le Dem created ARROW-252:
-----------------------------------

             Summary: Add implementation guidelines to the documentation
                 Key: ARROW-252
                 URL: https://issues.apache.org/jira/browse/ARROW-252
             Project: Apache Arrow
          Issue Type: Improvement
          Components: Format
            Reporter: Julien Le Dem


I'd like to add a paragraph to the documentation providing implementation guidelines:
An execution engine (or framework, or UDF executor, or storage engine, etc) can use only a subset of the arrow Arrow spec given the following constraints:

1) If it is only producing (and not consuming) arrow vectors.
 - any subset of the vector spec and the corresponding metadata can be implemented

2) If it is consuming *and* producing vectors
 - there is a minimal subset of vectors to be supported (To Be Defined)
 - production of a subset of vectors and their corresponding metadata is always fine
 - consumption of vectors should at least convert the unsupported input vectors to the supported subset (for example Timestamp.millis to timestamp.micros or int32 to int64)




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)