hudi-bot opened a new issue, #16293:
URL: https://github.com/apache/hudi/issues/16293
After HUDI-6960 is merged, there
*shouldExtractPartitionValuesFromPartitionPath* will correctly ignore partition
columns in requiredSchema.
When using the configs below, there will be read errors.
{code:java}
hoodie.datasource.read.extract.partition.values.from.path = true {code}
When the config above is added together with:
{code:java}
hoodie.schema.on.read.enable = true {code}
The query schema will be pruned to **{*}NOT{*}** contain any partition
columns.
When rebuilding parquet filters, file schema's columns are scanned against
querySchema. However, Hudi files (file schema) might still contain partition
columns. And when partition filters are being rebuilt with these file schema
against query schema, it will lead to partition columns not being found.
{code:java}
Caused by: java.lang.IllegalArgumentException: cannot found filter col
name：region from querySchema: table {
5: id: optional int
6: name: optional string
7: ts: optional long
}
at
org.apache.hudi.internal.schema.utils.InternalSchemaUtils.reBuildFilterName(InternalSchemaUtils.java:180)
{code}
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-7033
- Type: Bug
---
## Comments
24/Jun/24 07:47;geserdugarov;Merged a4fa3451916de11dc082792076b62013586dadaf
in linked MR 9994
refers to [non-merged MR 9889|https://github.com/apache/hudi/pull/9889];;;
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
