kingwind94 opened a new issue, #6694:
URL: https://github.com/apache/iceberg/issues/6694
### Query engine
flink 1.12
iceberg 0.13.2
### Question
As we know, position delete files should keep the file path and position. In
rewriting v2 tables, iceberg would validateNoNewDeletesForDataFiles and would
use the new position delete files' lower_bounds/upper_bounds for paths, to
check whether the new position deletes should apply to rewritten data files.
However, I found that the lower_bounds/upper_bounds of my position deletes
are incompelete as 'hdfs://ns2/user/', which would make iceberg validation
method thinks all of the new added position deletes should apply to rewritten
data files, and it will fail the rewrite process. Does any one know why the
lower_bounds/upper_bounds of position deletes are not correct?
"lower_bounds" : {
"array" : [ {
"key" : 2147483546,
"value" : "hdfs://ns2/user/"
}, {
"key" : 2147483545,
"value" : "\n\u0000\u0000\u0000\u0000\u0000\u0000\u0000"
} ]
},
"upper_bounds" : {
"array" : [ {
"key" : 2147483546,
"value" : "hdfs://ns2/user0"
}, {
"key" : 2147483545,
"value" : "ãå\u0005\u0000\u0000\u0000\u0000\u0000"
} ]
},
--
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: issues-unsubscr...@iceberg.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org
