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

Posted to commits@hudi.apache.org by "Manoj Govindassamy (Jira)" <ji...@apache.org> on 2022/01/06 17:05:00 UTC

[jira] [Closed] (HUDI-2703) [RFC-37] Metadata based bloom index

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

Manoj Govindassamy closed HUDI-2703.
------------------------------------
    Resolution: Duplicate

Closing this as a dup of HUDI-1822

> [RFC-37] Metadata based bloom index
> -----------------------------------
>
>                 Key: HUDI-2703
>                 URL: https://issues.apache.org/jira/browse/HUDI-2703
>             Project: Apache Hudi
>          Issue Type: Epic
>            Reporter: sivabalan narayanan
>            Assignee: sivabalan narayanan
>            Priority: Major
>              Labels: hudi-umbrellas
>             Fix For: 0.11.0
>
>
> Hudi has indices to assit in tagging incoming records. Most commonly used one is Bloom index. This involves looking up (loading) bloom from data files which could be time consuming and could have throttling impact in cloud stores like S3. So, proposing this RFC to add bloom as a special partition in metadata table and implement an index based on that. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)