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

Posted to commits@hudi.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/25 01:20:00 UTC

[jira] [Updated] (HUDI-4320) Make sure HoodieStorageConfig.PARQUET_WRITE_LEGACY_FORMAT_ENABLED could be specified by the writer

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

ASF GitHub Bot updated HUDI-4320:
---------------------------------
    Labels: pull-request-available  (was: )

> Make sure HoodieStorageConfig.PARQUET_WRITE_LEGACY_FORMAT_ENABLED could be specified by the writer
> --------------------------------------------------------------------------------------------------
>
>                 Key: HUDI-4320
>                 URL: https://issues.apache.org/jira/browse/HUDI-4320
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: Alexey Kudinkin
>            Assignee: Alexey Kudinkin
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.12.0
>
>
> Currently after [#4253|https://github.com/apache/hudi/pull/4253] no matter whether the user specified it explicitly or was relying on a default value this config value will be overridden (ie potentially reverting what have been specified by the user). As such, there's no way presently to enforce this config on the write side if your schema contains {{DecimalType}} fitting into the range.
> Instead the behavior should be to only override _default_ config value in cases when there's a {{DecimalType}} of expected range, and if this config have been specified by the user -- it should not be overridden.



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