[jira] [Commented] (ARROW-1329) [C++] Define "virtual table" interface
[
https://issues.apache.org/jira/browse/ARROW-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116046#comment-17116046
]
Wes McKinney commented on ARROW-1329:
-
Some time has passed but I plan to make some progress on this in June and July
> [C++] Define "virtual table" interface
> --
>
> Key: ARROW-1329
> URL: https://issues.apache.org/jira/browse/ARROW-1329
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
>Reporter: Wes McKinney
>Assignee: Wes McKinney
>Priority: Major
> Labels: dataframe
>
> The idea is that a virtual table may reference Arrow data that is not yet
> available in memory. The implementation will define the semantics of how
> columns are loaded into memory.
> A virtual column interface will need to accompany this. For example:
> {code:language=c++}
> std::shared_ptr vtable = ...;
> std::shared_ptr vcolumn = vtable->column(i);
> std::shared_ptr = vcolumn->Materialize();
> std::shared_ptr = vtable->Materialize();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARROW-1329) [C++] Define "virtual table" interface
[
https://issues.apache.org/jira/browse/ARROW-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912467#comment-16912467
]
Wes McKinney commented on ARROW-1329:
-
I'll address this issue as part of the "Data Frame" project. I think that's the
correct place to deal with late materialization / virtual columns, etc.
> [C++] Define "virtual table" interface
> --
>
> Key: ARROW-1329
> URL: https://issues.apache.org/jira/browse/ARROW-1329
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
>Reporter: Wes McKinney
>Assignee: Wes McKinney
>Priority: Major
> Labels: dataframe
>
> The idea is that a virtual table may reference Arrow data that is not yet
> available in memory. The implementation will define the semantics of how
> columns are loaded into memory.
> A virtual column interface will need to accompany this. For example:
> {code:language=c++}
> std::shared_ptr vtable = ...;
> std::shared_ptr vcolumn = vtable->column(i);
> std::shared_ptr = vcolumn->Materialize();
> std::shared_ptr = vtable->Materialize();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (ARROW-1329) [C++] Define "virtual table" interface
[
https://issues.apache.org/jira/browse/ARROW-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282175#comment-16282175
]
Wes McKinney commented on ARROW-1329:
-
There has been partial progress toward this. It may make sense to add a pure
virtual method to {{arrow::Table}} which ensures that all data is loaded into
memory. This will allow different Table implementations to define their own
logic for materialization
> [C++] Define "virtual table" interface
> --
>
> Key: ARROW-1329
> URL: https://issues.apache.org/jira/browse/ARROW-1329
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
>Reporter: Wes McKinney
> Fix For: 1.0.0
>
>
> The idea is that a virtual table may reference Arrow data that is not yet
> available in memory. The implementation will define the semantics of how
> columns are loaded into memory.
> A virtual column interface will need to accompany this. For example:
> {code:language=c++}
> std::shared_ptr vtable = ...;
> std::shared_ptr vcolumn = vtable->column(i);
> std::shared_ptr = vcolumn->Materialize();
> std::shared_ptr = vtable->Materialize();
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
