[jira] [Updated] (ARROW-7012) [C++] Clarify ChunkedArray chunking strategy and policy
[ https://issues.apache.org/jira/browse/ARROW-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neal Richardson updated ARROW-7012: --- Priority: Minor (was: Major) > [C++] Clarify ChunkedArray chunking strategy and policy > --- > > Key: ARROW-7012 > URL: https://issues.apache.org/jira/browse/ARROW-7012 > Project: Apache Arrow > Issue Type: New Feature > Components: C++ >Reporter: Neal Richardson >Assignee: Wes McKinney >Priority: Minor > Fix For: 1.0.0 > > > See discussion on ARROW-6784 and [https://github.com/apache/arrow/pull/5686]. > Among the questions: > * Do Arrow users control the chunking, or is it an internal implementation > detail they should not manage? > * If users control it, how do they control it? E.g. if I call Take and use a > ChunkedArray for the indices to take, does the chunking follow how the > indices are chunked? Or should we attempt to preserve the mapping of data to > their chunks in the input table/chunked array? > * If it's an implementation detail, what is the optimal chunk size? And when > is it worth reshaping (concatenating, slicing) input data to attain this > optimal size? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARROW-7012) [C++] Clarify ChunkedArray chunking strategy and policy
[ https://issues.apache.org/jira/browse/ARROW-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney updated ARROW-7012: Fix Version/s: 1.0.0 > [C++] Clarify ChunkedArray chunking strategy and policy > --- > > Key: ARROW-7012 > URL: https://issues.apache.org/jira/browse/ARROW-7012 > Project: Apache Arrow > Issue Type: New Feature > Components: C++ >Reporter: Neal Richardson >Priority: Major > Fix For: 1.0.0 > > > See discussion on ARROW-6784 and [https://github.com/apache/arrow/pull/5686]. > Among the questions: > * Do Arrow users control the chunking, or is it an internal implementation > detail they should not manage? > * If users control it, how do they control it? E.g. if I call Take and use a > ChunkedArray for the indices to take, does the chunking follow how the > indices are chunked? Or should we attempt to preserve the mapping of data to > their chunks in the input table/chunked array? > * If it's an implementation detail, what is the optimal chunk size? And when > is it worth reshaping (concatenating, slicing) input data to attain this > optimal size? -- This message was sent by Atlassian Jira (v8.3.4#803005)
