You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Alessandro Molina (Jira)" <ji...@apache.org> on 2022/10/12 13:54:00 UTC
[jira] [Updated] (ARROW-16616) [Python] Allow lazy evaluation of filters in Dataset and add Datset.filter method
[ https://issues.apache.org/jira/browse/ARROW-16616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessandro Molina updated ARROW-16616:
--------------------------------------
Fix Version/s: 11.0.0
(was: 10.0.0)
> [Python] Allow lazy evaluation of filters in Dataset and add Datset.filter method
> ---------------------------------------------------------------------------------
>
> Key: ARROW-16616
> URL: https://issues.apache.org/jira/browse/ARROW-16616
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Python
> Reporter: Alessandro Molina
> Assignee: Alessandro Molina
> Priority: Major
> Labels: pull-request-available
> Fix For: 11.0.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> To keep the {{Dataset}} api compatible with the {{Table}} one in terms of analytics capabilities, we should add a {{Dataset.filter}} method. The initial POC was based on {{_table_filter}} but that required materialising all the {{Dataset}} content after filtering as it returned an {{{}InMemoryDataset{}}}.
> Given that {{Scanner}} can filter a dataset without actually materialising the data until a final step happens, it would be good to have {{Dataset.filter}} return some form of lazy dataset when the filter is only stored aside and the Scanner is created when data is actually retrieved.
> PS: Also update {{test_dataset_filter}} test to use the {{Dataset.filter}} method
--
This message was sent by Atlassian Jira
(v8.20.10#820010)