-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Fix Hive FileIO closing with FileIOTracker #11782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for working on this @tom-s-powell. I was running into the same issue as you, see #11858. While testing your solution, I noticed that my logs are flooded with:
Did you try your fix in the wild? (I must admit it is not very easy to test). |
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
Fixes #11783.
HiveCatalog
currently uses a singleFileIO
instance that is passed to each newly instantiatedHiveTableOperations
/HiveViewOperations
. This issue isFileIOTracker
tracks each operation and results in the underlyingFileIO
being closed even when it is then going to be reused for futurenewTableOps
calls.This change will instead initialize a new
FileIO
instance so that they are 1:1 withHiveTableOperations
/HiveViewOperations
, thus safe to close when the operations go out of scope.