-
Notifications
You must be signed in to change notification settings - Fork 240
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
[BUG] create_map failed with java.lang.IllegalStateException: This is not supported yet #5180
Comments
As has been the case since the I'm checking if the |
Thank you for the clear repro case, by the way. |
Yep, I have confirmed that this is a regression. Apologies. I'm looking at what it will take to fix the problem. Stand by. |
I think I've found the problem. I'm testing a possible fix. |
Fixes NVIDIA#5180. Map lookup is currently supported only in cases where the keys are scalar values. In case the keys are specified as a vector (e.g. expressions), the plugin should fall back to CPU. NVIDIA#4944 introduced a bug in how literal signatures are specified for multiple data types. This breaks CPU fallback. This commit fixes the specification of literals-only `TypeSig`.
Fixes NVIDIA#5180. Map lookup is currently supported only in cases where the keys are scalar values. In case the keys are specified as a vector (e.g. expressions), the plugin should fall back to CPU. multiple data types. This breaks CPU fallback. This commit fixes the specification of literals-only `TypeSig`. Signed-off-by: MithunR <mythrocks@gmail.com>
@viadea: We have sorted out the CPU fallback for |
reopen auto-closed issue. need to confirm if we can close this or retarget to 22.06 |
Confirmed with @viadea , let's close this one. |
Below is the repro:
Error:
CPU Spark(Expected results):
Env:
22.04 snapshot jars
Is this a current limitation of create_map or a bug?
If it is a limitation, could we gracefully fallback to CPU?
The text was updated successfully, but these errors were encountered: