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/24 23:25:00 UTC

[jira] [Closed] (HUDI-3144) Metadata table getRecordsByKeys() operations with inline reading has poor performance

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

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

The core issue is discussed under - https://issues.apache.org/jira/browse/HUDI-3301. Closing this as a DUP.

> Metadata table getRecordsByKeys() operations with inline reading has poor performance
> -------------------------------------------------------------------------------------
>
>                 Key: HUDI-3144
>                 URL: https://issues.apache.org/jira/browse/HUDI-3144
>             Project: Apache Hudi
>          Issue Type: Task
>          Components: metadata
>            Reporter: Manoj Govindassamy
>            Assignee: Manoj Govindassamy
>            Priority: Blocker
>             Fix For: 0.11.0
>
>
> When the metadata index lookups is done for several thousands of keys, the keys are looked up in metadata table partitions in a serial fashion key by key, leading to the overall delay in the index lookup.
>  # When the indexes are laid out in multiple file groups, the lookup can be parallelized at the filegroup level
>  # Even within a single filegroup, sorted keys can be split and the lookup can be done in parallel. 
>  
>  



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