Fix Hive FileIO closing with FileIOTracker #11782
Open
+6
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.