pvary closed issue #10006: HiveLock is chosen according to new table metadata
URL: https://github.com/apache/iceberg/issues/10006
--
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.
pvary commented on issue #10006:
URL: https://github.com/apache/iceberg/issues/10006#issuecomment-2011257443
@lirui-apache: You are right. I thought that we use the old locking
mechanism. We need a secure migration path if it is possible to access the old
metadata. Also make sure that we ha
lirui-apache commented on issue #10006:
URL: https://github.com/apache/iceberg/issues/10006#issuecomment-2011212269
@szehon-ho @pvary I'm using this test case to demonstrate the issue:
```java
final int parallel = 2;
ThreadPoolExecutor pool = (ThreadPoolExecutor)
Executors.
szehon-ho commented on issue #10006:
URL: https://github.com/apache/iceberg/issues/10006#issuecomment-2010260196
Yes this is possible, I think we tried to document the limitations of this
flag here:
https://iceberg.apache.org/docs/latest/configuration/#hadoop-configuration fyi
@pvary
lirui-apache commented on issue #10006:
URL: https://github.com/apache/iceberg/issues/10006#issuecomment-2009763001
@nastra I'm trying to work out a test case to verify if the issue is valid.
Until then, yes I think it's more like a question.
--
This is an automated message from the Apach
nastra commented on issue #10006:
URL: https://github.com/apache/iceberg/issues/10006#issuecomment-2009657347
@lirui-apache this seems more like a question than a bug?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
lirui-apache opened a new issue, #10006:
URL: https://github.com/apache/iceberg/issues/10006
### Apache Iceberg version
main (development)
### Query engine
None
### Please describe the bug 🐞
When `HiveTableOperations` commits, which kind of `HiveLock` to use
