-
Notifications
You must be signed in to change notification settings - Fork 245
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] Spark-3.4 - Integration test failures due to GpuCreateDataSourceTableAsSelectCommand #8019
Comments
Difference in Physical Plans (using logTransformations config): Spark 3.3.0:
Spark 3.4.0
|
Upon further investigation, Spark 3.3 uses GpuDataWritingCommandExec implementation of
But GpuExecutedCommandExec implementation of
That's what's causing the exception thrown in these test failures. There is a GpuRunnableCommandExec which essentially is the same implementation as GpuDataWritingCommandExec but is not currently used, but takes a GpuRunnableCommand as what would be needed. I think we would use that instead of GpuExecutedCommandExec. @jlowe any thoughts on this, since GpuExecutedCommandExec would be the normal replacement but it's implementation is done the way it is due to Delta Lake? |
IMO GpuRunnableCommand should not exist, see #7619. GpuExecutedCommandExec is the right replacement here. The problem seems to be primarily with GpuDataWritingCommand. Per the discussion in #7619 that Command arguably should return rows and not complain when |
@NVnavkumar I added the test |
Describe the bug
Some of the integration tests are failing due to Exception thrown from GpuCreateDataSourceTableAsSelectCommand.
Failing tests:
Exception stack trace:
Not certain if this is related but we do see CommandResultExec is not supported on GPU
Steps/Code to reproduce bug
Run integration tests for failing tests
cd spark-rapids/integration_tests/
./run_pyspark_from_build.sh -k <name of test>
//Example : ./run_pyspark_from_build.sh -k test_write_save_table
Expected behavior
Environment details (please complete the following information)
local
The text was updated successfully, but these errors were encountered: