Closed razajafri closed 4 years ago
@jlowe has hypothesized from a very brief look at the trace that the plugin might be passing an AttributeReference
to the GpuSortExec instead of the GpuAttributeReference
. I am looking into this further
Upon further inspection I confirmed that it is indeed the case where spark tries to recreate the GpuSortOrder from outputs and tries to pass Attribute
in place of GpuAttribute
which causes a crash.
It was decided that we will have to get rid of the GpuAttribute
and any objects that are currently taking in GpuExpression
as a parameter will have to be changed to accept Expression
. I have also added a unit test that tests this case as part of this PR
Describe the bug While running a query on Jupyter notebook. The GpuSortOrder is throwing the following exception.
Steps/Code to reproduce bug Load the attached notebook and run it
Expected behavior It should run without a problem on the GPU just like it does on the CPU