[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhaojing Yu updated HUDI-3626:
------------------------------
Fix Version/s: 0.13.0
(was: 0.12.1)
> Refactor TableSchemaResolver to remove `includeMetadataFields` flags
> --------------------------------------------------------------------
>
> Key: HUDI-3626
> URL: https://issues.apache.org/jira/browse/HUDI-3626
> Project: Apache Hudi
> Issue Type: Bug
> Reporter: Alexey Kudinkin
> Assignee: Alexey Kudinkin
> Priority: Critical
> Fix For: 0.13.0
>
>
> Currently, `TableSchemaResolver` to pass `includeMetadataFields` in its APIs
> that would selectively remove metadata fields from the returned schemas.
> There are multiple issues with this flag:
> # It's applied inconsistently: sometimes it just means that meta fields
> {_}won't be added{_}, and sometimes it means fields _would be removed_ even
> if present
> # This flag actually spells the usage context into TableSchemaResolver: it's
> highly contextual whether caller wants to remove, omit such meta-fields, or
> take the schema as is and should not be spilled into the Resolver itself.
> # B/c of it there's no way to know actually what was actual schema the data
> was written with (b/c flag might not only omit, but also change the original
> schema)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
