HIVE-25686: UDFSpace result length calculation is incorrect after HADOOP-17901 and HADOOP-17905 #2786
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.
What changes were proposed in this pull request?
After the application of HADOOP-17901 and HADOOP-17905 they changed the backing array increment logic which is causing issues in the UDFSpace class.
Why are the changes needed?
The previous
result.getBytes().lengthis returning incorrect size which is causing error in the result output. By changing this method call toresult.getLength()the size calculation is correct again any the original behaviour is restored.Example of the UDFSpace behaviour with the different method calls:
Note that the issue is only present with Hadoop version that contains HADOOP-17901 and HADOOP-17905.
Does this PR introduce any user-facing change?
No
How was this patch tested?
The change was tested on live cluster and also in the new qtest that was introduced in the scope of this patch.