[
https://issues.apache.org/jira/browse/ARROW-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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<VirtualTable> vtable = ...;
> std::shared_ptr<VirtualColumn> vcolumn = vtable->column(i);
> std::shared_ptr<Column> = vcolumn->Materialize();
> std::shared_ptr<Table> = vtable->Materialize();
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
