zhengruifeng opened a new pull request, #55529:
URL: https://github.com/apache/spark/pull/55529
### What changes were proposed in this pull request?
Since `QueryTest` extends `SparkFunSuite with QueryTestBase with PlanTest`,
and `PlanTest` extends `SparkFunSuite with PlanTestBase`, mixing
`SparkFunSuite` in again alongside `QueryTest` or `PlanTest` in the `extends`
list is a no-op.
Linearization:
```
QueryTest -> SparkFunSuite
\> QueryTestBase
\> PlanTest -> SparkFunSuite
\> PlanTestBase
PlanTest -> SparkFunSuite
\> PlanTestBase
```
Cleanup across 7 test files in `sql-catalyst`, `sql-core`, and `sql-hive`:
- `extends SparkFunSuite with QueryTest` -> `extends QueryTest` (3 files)
- `MapStatusEndToEndSuite`
- `ExecutorSideSQLConfSuite`
- `ParquetCommitterSuite` (also has `with LocalSparkContext`, retained)
- `extends SparkFunSuite with PlanTest` -> `extends PlanTest` (3 files)
- `ConstraintPropagationSuite`
- `ExtractPredicatesWithinOutputSetSuite`
- `FiltersSuite`
- `extends SparkFunSuite with SQLHelper with AdaptiveSparkPlanHelper with
PlanTest` -> `extends PlanTest with SQLHelper with AdaptiveSparkPlanHelper` (1
file)
- `SparkSessionExtensionSuite`
Also removed the now-unused `SparkFunSuite` imports.
### Why are the changes needed?
Follow-up to
[SPARK-56591](https://issues.apache.org/jira/browse/SPARK-56591), which removed
the analogous `QueryTest with SharedSparkSession` redundancy. Keeps the
`extends` clauses minimal and removes imports that no longer serve any purpose.
### Does this PR introduce _any_ user-facing change?
No. Test-only change.
### How was this patch tested?
`dev/scalastyle` passes. Existing tests in the affected suites exercise the
unchanged test logic.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (model: claude-opus-4-7)
--
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]
