You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Ben Kietzman (Jira)" <ji...@apache.org> on 2021/01/07 20:15:00 UTC
[jira] [Updated] (ARROW-10437) [C++][Dataset] Ensure virtual
columns are not materialized on write
[ https://issues.apache.org/jira/browse/ARROW-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben Kietzman updated ARROW-10437:
---------------------------------
Fix Version/s: (was: 3.0.0)
4.0.0
> [C++][Dataset] Ensure virtual columns are not materialized on write
> -------------------------------------------------------------------
>
> Key: ARROW-10437
> URL: https://issues.apache.org/jira/browse/ARROW-10437
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 2.0.0
> Reporter: Ben Kietzman
> Assignee: Ben Kietzman
> Priority: Major
> Labels: dataset
> Fix For: 4.0.0
>
>
> If a column is virtual on read and will remain virtual after writing then materializing and grouping on it is a pure waste. Maybe Partitioning::Partition should take a "already known" partition expression and only group on columns not in it?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)