[SPARK-57328][SQL] Extract matchedIdentifier into a static, resolver-parameterized helper ## What changes were proposed in this pull request? This PR refactors the relation-identifier suffix-match logic (`matchedIdentifier`) out of the `ResolveHints.ResolveJoinStrategyHints` rule and into a static, resolver-parameterized helper, so the logic can be shared without depending on fixed-point rule state. - Added a static `ResolveHints.matchedIdentifier(identInHint, identInQuery, resolver)` helper that takes the `resolver: Resolver` (i.e. `(String, String) => Boolean`) as an explicit parameter. - Moved the explanatory doc comment (describing the tail-match semantics and the catalog-independent comparison) onto the static helper. - `ResolveJoinStrategyHints` now keeps a thin private `matchedIdentifier` that delegates to the static helper, passing its `resolver`. Passing the `resolver` in explicitly gives both the fixed-point analyzer and the single-pass resolver one source of truth for hint-to-relation matching, without either having to depend on the other's rule state. No behavior change: the helper body is identical to the original. ## How was this patch tested? Existing join-hint resolution test coverage (e.g. join hint suites) pins the behavior; this is a pure extraction with no functional change. ## Was this patch authored or co-authored using generative AI tooling? No Closes #56478 from dtenedor/refactor-matched-identifier. Authored-by: Daniel Tenedorio <daniel.tenedorio@databricks.com> Signed-off-by: Daniel Tenedorio <daniel.tenedorio@databricks.com>
Spark is a unified analytics engine for large-scale data processing. It provides high-level APIs in Scala, Java, Python, and R (Deprecated), and an optimized engine that supports general computation graphs for data analysis. It also supports a rich set of higher-level tools including Spark SQL for SQL and DataFrames, pandas API on Spark for pandas workloads, MLlib for machine learning, GraphX for graph processing, and Structured Streaming for stream processing.
You can find the latest Spark documentation, including a programming guide, on the project web page. This README file only contains basic setup instructions.
| Branch | Status |
|---|---|
| master |  |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
| branch-4.x |  |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
| branch-4.2 |  |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
| branch-4.1 |  |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
| branch-4.0 |  |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
| branch-3.5 |  |
 |
Spark is built using Apache Maven. To build Spark and its example programs, run:
./build/mvn -DskipTests clean package
(You do not need to do this if you downloaded a pre-built package.)
More detailed documentation is available from the project site, at “Building Spark”.
For general development tips, including info on developing Spark using an IDE, see “Useful Developer Tools”.
The easiest way to start using Spark is through the Scala shell:
./bin/spark-shell
Try the following command, which should return 1,000,000,000:
scala> spark.range(1000 * 1000 * 1000).count()
Alternatively, if you prefer Python, you can use the Python shell:
./bin/pyspark
And run the following command, which should also return 1,000,000,000:
>>> spark.range(1000 * 1000 * 1000).count()
Spark also comes with several sample programs in the examples directory. To run one of them, use ./bin/run-example <class> [params]. For example:
./bin/run-example SparkPi
will run the Pi example locally.
You can set the MASTER environment variable when running examples to submit examples to a cluster. This can be spark:// URL, “yarn” to run on YARN, and “local” to run locally with one thread, or “local[N]” to run locally with N threads. You can also use an abbreviated class name if the class is in the examples package. For instance:
MASTER=spark://host:7077 ./bin/run-example SparkPi
Many of the example programs print usage help if no params are given.
Testing first requires building Spark. Once Spark is built, tests can be run using:
./dev/run-tests
Please see the guidance on how to run tests for a module, or individual tests.
There is also a Kubernetes integration test, see resource-managers/kubernetes/integration-tests/README.md
Spark uses the Hadoop core library to talk to HDFS and other Hadoop-supported storage systems. Because the protocols have changed in different versions of Hadoop, you must build Spark against the same version that your cluster runs.
Please refer to the build documentation at “Specifying the Hadoop Version and Enabling YARN” for detailed guidance on building for a particular distribution of Hadoop, including building for particular Hive and Hive Thriftserver distributions.
Please refer to the Configuration Guide in the online documentation for an overview on how to configure Spark.
Please review the Contribution to Spark guide for information on how to get started contributing to the project.
