[
https://issues.apache.org/jira/browse/ARROW-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041231#comment-17041231
]
Francois Saint-Jacques commented on ARROW-7808:
-----------------------------------------------
I concur with [~bkietz] here, prefer a high-level approach, e.g. it should
start with the factory, dataset and getting the result of a scan, then you can
expose more and more of the inner classes, instead of 1-1 with all the classes.
Also note that a JNI bridge means one more maintenance burden; we already did a
bunch of renames and it was cumbersome to do it for each "native" binding too,
e.g. DataSource is now called Source.
> [Java][Dataset] Implement Datasets Java API
> --------------------------------------------
>
> Key: ARROW-7808
> URL: https://issues.apache.org/jira/browse/ARROW-7808
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++ - Dataset, Java
> Reporter: Hongze Zhang
> Priority: Major
> Labels: dataset
>
> Porting following C++ Datasets APIs to Java:
> * DataSource
> * DataSourceDiscovery
> * DataFragment
> * Dataset
> * Scanner
> * ScanTask
> * ScanOptions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
