GH-49034 [C++][Gandiva] Fix binary_string to not trigger error for nu… #49035
+23
−10
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.
…ll strings.
Rationale for this change
Fixes GH-49034.
The binary_string funcion will attempt to allocate 0 bytes of memory, which results in a null ptr being returned and the function interprets that as an error.
What changes are included in this PR?
Add kCanReturnErrors to the function definition to match other string functions.
Move the check for 0 byte length input earlier in the binary_string function to prevent the 0 allocation.
Add a unit test.
Are these changes tested?
Yes, unit and integration testing.
Are there any user-facing changes?
No.