-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-enables partial regex support for octal digits on the GPU #4735
Re-enables partial regex support for octal digits on the GPU #4735
Conversation
Signed-off-by: Navin Kumar <navink@nvidia.com>
…nspiler Signed-off-by: Navin Kumar <navink@nvidia.com>
Signed-off-by: Navin Kumar <navink@nvidia.com>
Signed-off-by: Navin Kumar <navink@nvidia.com>
Just a small question. If we can parse them properly why not switch them over to something that CUDF does support? like hex digits? |
sql-plugin/src/main/scala/com/nvidia/spark/rapids/RegexParser.scala
Outdated
Show resolved
Hide resolved
CUDF actually also doesn't support hex digits in the range that corresponds to 128-255 |
Signed-off-by: Navin Kumar <navink@nvidia.com>
Signed-off-by: Navin Kumar <navink@nvidia.com>
build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I am not sure why the build failed but it seems unrelated.
build |
Fixes #4409.
Since a couple of underlying
libcudf
issues with octal digit support in regular expression have now been resolved, this code re-enables octal digit support with the appropriate transpiling from Java Pattern support to libcudf regular expression format. A couple of known limitations:\200
to\377
are not supported bylibcudf
, so this will still fallback to CPU[\022]
) inlibcudf
, so this will also fallback to CPUDocumentation has been updated to reflect these limitations.