DRILL-8495: Tried to remove unmanaged buffer #2913
Merged
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.
DRILL-8495: Tried to remove unmanaged buffer
The root cause of the issue is that multiple HiveWriters use the same
DrillBuf
and during execution they may reallocate the buffer if size of the buffer is not enough for a value (256 bytes+). SincedrillBuf.reallocIfNeeded(int size)
returns a new instance ofDrillBuf
, all other writers still have a reference for the old one buffer, which afterdrillBuf.reallocIfNeeded(int size)
execution is unmanaged now.Description
HiveValueWriterFactory
now creates a uniqueDrillBif
for each writer.HiveWriters are actually used one-by-one and we could utilize a single buffer for all the writers. To do this, I could create a class holder for
DrillBuf
, so each writer has a reference for the same holder, where will be stored a new buffer from everydrillBuf.reallocIfNeeded(int size)
call. But I thought that such logic looked slightly confusing and I decided just to let each HiveWriter use its own buffer.Documentation
-
Testing
Add a new unit test to query a Hive table with variable-length values of Binary, VarChar, Char and String types.