You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Vinoth Chandar (Jira)" <ji...@apache.org> on 2019/11/11 13:16:00 UTC

[jira] [Updated] (HUDI-145) Limit the amount of partitions considered for GlobalBloomIndex

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

Vinoth Chandar updated HUDI-145:
--------------------------------
    Description: Currently, global bloom index will check inputs against files in all partitions.. In lot of cases, the user may know a range of partitions actually impacted from updates clearly (e.g upstream system drops updates older than a year, ... )..  In such a scenario,it may make sense to support an option for Global bloom to control how many partitions you want to match against, to gain performance. 

> Limit the amount of partitions considered for GlobalBloomIndex
> --------------------------------------------------------------
>
>                 Key: HUDI-145
>                 URL: https://issues.apache.org/jira/browse/HUDI-145
>             Project: Apache Hudi (incubating)
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Vinoth Chandar
>            Assignee: Vinoth Chandar
>            Priority: Major
>
> Currently, global bloom index will check inputs against files in all partitions.. In lot of cases, the user may know a range of partitions actually impacted from updates clearly (e.g upstream system drops updates older than a year, ... )..  In such a scenario,it may make sense to support an option for Global bloom to control how many partitions you want to match against, to gain performance. 



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