[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kudinkin updated HUDI-3626:
--
Priority: Blocker (was: Major)
> 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: Blocker
> Fix For: 0.12.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.1#820001)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kudinkin updated HUDI-3626:
--
Fix Version/s: 0.12.0
> 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: Major
> Fix For: 0.12.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.1#820001)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Xu updated HUDI-3626:
-
Sprint: 2022/09/05 (was: 2022/08/22)
> 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.12.1
>
>
> 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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Xu updated HUDI-3626:
-
Sprint: (was: 2022/09/05)
> 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.12.1
>
>
> 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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Sumit updated HUDI-3626:
--
Priority: Critical (was: Blocker)
> 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.12.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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Sumit updated HUDI-3626:
--
Fix Version/s: 0.12.1
(was: 0.12.0)
> 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.12.1
>
>
> 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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Sumit updated HUDI-3626:
--
Sprint: 2022/08/22
> 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.12.1
>
>
> 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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yue Zhang updated HUDI-3626:
Fix Version/s: 0.14.0
(was: 0.13.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.14.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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Wason updated HUDI-3626:
-
Fix Version/s: 0.14.1
(was: 0.14.0)
> 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.14.1
>
>
> 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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Sumit updated HUDI-3626:
--
Sprint: 2022/12/26
> 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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Xu updated HUDI-3626:
-
Sprint: 2023-01-09 (was: 0.13.0 Final Sprint)
> 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)
[jira] [Updated] (HUDI-3626) Refactor TableSchemaResolver to remove `includeMetadataFields` flags
[
https://issues.apache.org/jira/browse/HUDI-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated HUDI-3626:
-
Sprint: (was: )
> 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)
