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/05/04 19:11:00 UTC

[jira] [Assigned] (HUDI-4036) Investigate whether meta fields could be omitted completely

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

Alexey Kudinkin reassigned HUDI-4036:
-------------------------------------

    Assignee: Alexey Kudinkin

> Investigate whether meta fields could be omitted completely
> -----------------------------------------------------------
>
>                 Key: HUDI-4036
>                 URL: https://issues.apache.org/jira/browse/HUDI-4036
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: Alexey Kudinkin
>            Assignee: Alexey Kudinkin
>            Priority: Critical
>             Fix For: 0.12.0
>
>
> Currently, even when meta fields are not populated, we still insert empty-string columns to adhere to the expected schema.
> This has a non-trivial overhead of ~20% (relative to just writing dataset as is), since Spark had to essentially "re-write" the original row with prepended new fields.
> We should investigate whether it's feasible to avoid adding empty-string columns completely if meta-fields are disabled.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)