pratham76 opened a new pull request, #59256:
URL: https://github.com/apache/spark/pull/59256
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'common/utils/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster
reviews in your PR. See the examples below.
1. If you refactor some codes with changing classes, showing the class
hierarchy will help reviewers.
2. If you fix some SQL features, you can provide some references of other
DBMSes.
3. If there is design documentation, please add the link.
4. If there is a discussion in the mailing list, please add the link.
-->
Add RemoveRedundantAliases.ruleName to nonExcludableRules in
Optimizer.scala, so it can no longer be turned off via
spark.sql.optimizer.excludedRules.
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
EliminateSerialization collapses a DeserializeToObject/SerializeFromObject
pair and wraps the result in an exprId-preserving Alias typed as ObjectType.
RemoveRedundantAliases is what normally strips that alias back out before
execution. If a user excludes RemoveRedundantAliases via
spark.sql.optimizer.excludedRules, the ObjectType-typed alias leaks into the
physical plan, and both the codegen path (GenerateUnsafeProjection) and the
interpreted fallback (InterpretedUnsafeProjection) fail because neither
supports projecting an ObjectType field. This can be reproduced with any typed
Dataset operation chain that triggers EliminateSerialization (e.g.
groupByKey().mapGroups().mapPartitions()), with RemoveRedundantAliases excluded:
```
withSQLConf(
"spark.sql.optimizer.excludedRules" ->
"org.apache.spark.sql.catalyst.optimizer.RemoveRedundantAliases") {
Seq(ClassData("a", 1), ClassData("a", 2), ClassData("b", 3)).toDS()
.groupByKey(_.a)
.mapGroups { (k, it) => ClassData(k, it.map(_.b).sum) }
.mapPartitions(iter => iter)
.collect()
}
```
This throws a codegen CompileException rather than failing gracefully. Other
rules in nonExcludableRules already exist precisely to prevent excludedRules
from leaking unsupported/unevaluable plan nodes into execution, so
RemoveRedundantAliases belongs in that list for the same reason.
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
new features, bug fixes, or other behavior changes. Documentation-only updates
are not considered user-facing changes.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description and/or an example to show the
behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released Spark versions or within the unreleased branches such as master.
If no, write 'No'.
-->
Yes, but only in a narrow, previously-broken configuration:
`spark.sql.optimizer.excludedRules` can no longer disable
RemoveRedundantAliases. Attempting to do so now logs the existing "was not
excluded... because this rule is a non-excludable rule" warning instead of
crashing at execution time. No change in behavior when RemoveRedundantAliases
is not excluded (the default, and the only previously-supported configuration).
### How was this patch tested?
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
If benchmark tests were added, please run the benchmarks in GitHub Actions
for the consistent environment, and the instructions could accord to:
https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
-->
Updated the existing reproduction test in `DatasetSuite` into a permanent
regression test, asserting the typed Dataset pipeline now completes
successfully even with RemoveRedundantAliases in excludedRules.
### Was this patch authored or co-authored using generative AI tooling?
<!--
If generative AI tooling has been used in the process of authoring this
patch, please include the
phrase: 'Generated-by: ' followed by the name of the tool and its version.
If no, write 'No'.
Please refer to the [ASF Generative Tooling
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
-->
Generated-by: Claude Sonnet 5
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
