You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Alexey Kudinkin (Jira)" <ji...@apache.org> on 2022/06/01 21:40:00 UTC
[jira] [Assigned] (HUDI-4176) TableSchemaResolver fetches/parses HoodieCommitMetadata multiple times while extracting Schema
[ https://issues.apache.org/jira/browse/HUDI-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Kudinkin reassigned HUDI-4176:
-------------------------------------
Assignee: Alexey Kudinkin
> TableSchemaResolver fetches/parses HoodieCommitMetadata multiple times while extracting Schema
> ----------------------------------------------------------------------------------------------
>
> Key: HUDI-4176
> URL: https://issues.apache.org/jira/browse/HUDI-4176
> Project: Apache Hudi
> Issue Type: Bug
> Affects Versions: 0.11.0
> Reporter: Alexey Kudinkin
> Assignee: Alexey Kudinkin
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.11.1
>
>
> We've recently discovered that TableSchemaResolver does a lot of throw-away work during initialization and basic schema reading performed by Spark Datasource (see screenshot).
> This poses a problem for large tables where HoodieCommitMetadata is of non-trivial size (100s of Mbs).
> We'd minimize amount of throw-away work done by `TableSchemaResolver` and try to re-use read/parsed commits' metadata as much as possible.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)