GpuStringSplit now honors thespark.rapids.sql.regexp.enabled
configuration option
#5297
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 #5130.
This allows GpuStringSplit to honor the
spark.rapids.sql.regexp.enabled
configuration flag. Desired behavior is to fallback to CPU when using a valid regular expression, but still use the GPU when using a simple string or when the pattern can be converted into a simple string. This is done by using the existingcheckRegExp
method that already handles the logic when the transpilation to a simple string will still work, and also when the parameter is not an actual regular expression.Here's some PySpark code to test this branch:
Signed-off-by: Navin Kumar [email protected]