Skip to content
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

Comet fails on limit operator with negative limit parameter #287

Closed
viirya opened this issue Apr 18, 2024 · 0 comments · Fixed by #288
Closed

Comet fails on limit operator with negative limit parameter #287

viirya opened this issue Apr 18, 2024 · 0 comments · Fixed by #288
Assignees
Labels
bug Something isn't working

Comments

@viirya
Copy link
Member

viirya commented Apr 18, 2024

Describe the bug

Another Spark SQL test failure when working in #250.

DataFrameSuite:

- offset *** FAILED *** (36 milliseconds)
[info]   org.apache.spark.SparkException: [INTERNAL_ERROR] The Spark SQL phase planning failed with an internal error. You hit a bug in Spark or the Spark plugins you use. Please, report this bug to the corresponding communities or vendors, and provide the full stack trace.
[info]   at org.apache.spark.SparkException$.internalError(SparkException.scala:88)
...
  Cause: java.lang.AssertionError: assertion failed: limit should be greater or equal to zero
[info]   at scala.Predef$.assert(Predef.scala:223)
[info]   at org.apache.comet.serde.QueryPlanSerde$.operator2Proto(QueryPlanSerde.scala:1847)
[info]   at org.apache.comet.CometSparkSessionExtensions$CometExecRule.org$apache$comet$CometSparkSessionExtensions$CometExecRule$$transform1$1(CometSparkSessionExtensions.scala:232)

Steps to reproduce

No response

Expected behavior

No response

Additional context

No response

@viirya viirya added the bug Something isn't working label Apr 18, 2024
@viirya viirya self-assigned this Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant