[jira] [Resolved] (ARROW-8065) [C++][Dataset] Untangle Dataset, Fragment and ScanOptions

["Ben Kietzman (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-8065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ben Kietzman resolved ARROW-8065.
---------------------------------
    Fix Version/s: 1.0.0
       Resolution: Fixed

Issue resolved by pull request 7000
[https://github.com/apache/arrow/pull/7000]

> [C++][Dataset] Untangle Dataset, Fragment and ScanOptions
> ---------------------------------------------------------
>
>                 Key: ARROW-8065
>                 URL: https://issues.apache.org/jira/browse/ARROW-8065
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Francois Saint-Jacques
>            Assignee: Francois Saint-Jacques
>            Priority: Major
>              Labels: dataset, pull-request-available
>             Fix For: 1.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently: a fragment is a product of a scan; it is a lazy collection of scan tasks corresponding to a data source which is logically singular (like a single file, a single row group, ...). It would be more useful if instead a fragment were the direct object of a scan; one scans a fragment (or a collection of fragments):
>  # Remove {{ScanOptions}} from Fragment's properties and move it into {{Fragment::Scan}} parameters.
>  # Remove {{ScanOptions}} from {{Dataset::GetFragments}}. We can provide an overload to support predicate pushdown in FileSystemDataset and UnionDataset {{Dataset::GetFragments(std::shared_ptr<Expression> predicate)}}.
>  # Expose lazy accessor to Fragment::physical_schema()
>  # Consolidate ScanOptions and ScanContext
> This will lessen the cognitive dissonance between fragments and files since fragments will no longer include references to scan properties.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)