Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[BUG] Build fails for Spark 3.3 due to extra arguments to mapKeyNotExistError #5351

Closed
res-life opened this issue Apr 28, 2022 · 1 comment · Fixed by #5352
Closed

[BUG] Build fails for Spark 3.3 due to extra arguments to mapKeyNotExistError #5351

res-life opened this issue Apr 28, 2022 · 1 comment · Fixed by #5352
Assignees
Labels
audit_3.3.0 Audit related tasks for 3.3.0 bug Something isn't working build Related to CI / CD or cleanly building P0 Must have for release

Comments

@res-life
Copy link
Collaborator

Describe the bug
Build is failing against Spark 3.3:

[INFO] Compiling 271 Scala sources and 29 Java sources to /home/c/code/2-spark-rapids/sql-plugin/target/spark330/classes ...
[ERROR] [Error] /home/c/code/2-spark-rapids/sql-plugin/src/main/330+/scala/com/nvidia/spark/rapids/shims/RapidsErrorUtils.scala:35: not enough arguments for method mapKeyNotExistError: (key: Any, dataType: org.apache.spark.sql.types.DataType, context: String)NoSuchElementException.
Unspecified value parameter context.
@res-life res-life added bug Something isn't working ? - Needs Triage Need team to review and classify build Related to CI / CD or cleanly building P0 Must have for release audit_3.3.0 Audit related tasks for 3.3.0 labels Apr 28, 2022
@res-life res-life self-assigned this Apr 28, 2022
@res-life
Copy link
Collaborator Author

@sameerz sameerz removed the ? - Needs Triage Need team to review and classify label Apr 28, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
audit_3.3.0 Audit related tasks for 3.3.0 bug Something isn't working build Related to CI / CD or cleanly building P0 Must have for release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants