update the plugin version to v26.06.0

[nvliyuan]

The PR is to update the plugin version to latest v26.06.0.

Summary

• Updated RAPIDS Accelerator plugin references from v26.02.0 to v26.06.0 across docs, notebooks, init scripts, and examples.
• Updated matching RAPIDS/cuDF/cuML release references in UDF and ML example setup docs.

Test plan

• git diff --check
• Searched for remaining 26.02 / 26.04 RAPIDS plugin references and found none.

Signed-off-by: liyuan yuali@nvidia.com

[greptile-apps]

Greptile Summary

This PR performs a blanket version bump of the RAPIDS Accelerator for Apache Spark plugin from 26.02.0 to 26.06.0 across all documentation, notebooks, init scripts, shell scripts, and configuration files in the repository.

• All 23 changed files are documentation or configuration artifacts (no functional source-code changes); version strings, Maven URLs, conda environment names, and PYTHONPATH references are updated uniformly from 26.02.0 to 26.06.0.
• The pom.xml rapids4spark.version property and the docker-compose.yaml default RAPIDS_VERSION are both bumped, ensuring build and containerized workflows pick up the new release.

Confidence Score: 5/5

Safe to merge — all changes are version-string updates across documentation, notebooks, and configuration files with no functional code modified.

Every changed line is a version reference swap (26.02.0 → 26.06.0) in docs, init scripts, notebooks, and config files. The Maven URLs, conda env names, PYTHONPATH entries, and build-arg defaults are all updated consistently. No logic, tests, or production code paths are touched.

No files require special attention.

Important Files Changed

Filename	Overview
examples/UDF-Examples/RAPIDS-accelerated-UDFs/pom.xml	rapids4spark.version bumped from 26.02.0 to 26.06.0; no other changes.
examples/spark-connect-gpu/server/docker-compose.yaml	Default RAPIDS_VERSION build arg updated from 26.02.0 to 26.06.0.
examples/ML+DL-Examples/Optuna-Spark/optuna-examples/databricks/init_optuna.sh	SPARK_RAPIDS_VERSION variable bumped from 26.02.0 to 26.06.0; download URL is parametric so it updates automatically.
examples/ML+DL-Examples/Optuna-Spark/optuna-examples/databricks/start_cluster.sh	PYTHONPATH jar filename updated from 26.02.0 to 26.06.0 in the cluster JSON config.
examples/SQL+DF-Examples/tpcds/notebooks/TPCDS-SF10.ipynb	rapids_version variable updated from 26.02.0 to 26.06.0.
docs/get-started/xgboost-examples/csp/databricks/init.sh	wget download URL for the RAPIDS jar updated from 26.02.0 to 26.06.0.
examples/ML+DL-Examples/Spark-Rapids-ML/pca/README.md	Download section updated to 26.06.0 with corrected anchor; trailing whitespace removed.
examples/ML+DL-Examples/Optuna-Spark/optuna-examples/optuna-dataframe.ipynb	SPARK_RAPIDS_VERSION constant updated to 26.06.0; one historical notebook output line contains a minor numeric difference discussed separately.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: Version Bump 26.02.0 → 26.06.0] --> B[Documentation]
    A --> C[Notebooks]
    A --> D[Scripts / Config]

    B --> B1[docs/databricks.md]
    B --> B2[preparation-python.md]
    B --> B3[preparation-scala.md]
    B --> B4[pca/README.md]
    B --> B5[tpcds/README.md]
    B --> B6[UDF README.md]
    B --> B7[spark-connect README.md]
    B --> B8[Optuna README.md]
    B --> B9[tools/databricks README.md]

    C --> C1[optuna-dataframe.ipynb]
    C --> C2[pca.ipynb]
    C --> C3[micro-benchmarks-gpu.ipynb]
    C --> C4[TPCDS-SF10.ipynb]
    C --> C5[MortgageETL.ipynb / mortgage-ETL.ipynb]
    C --> C6[taxi-ETL.ipynb × 2]

    D --> D1[init.sh / init_optuna.sh]
    D --> D2[start_cluster.sh]
    D --> D3[extract-cudf-libs.sh]
    D --> D4[pom.xml]
    D --> D5[docker-compose.yaml]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[PR: Version Bump 26.02.0 → 26.06.0] --> B[Documentation]
    A --> C[Notebooks]
    A --> D[Scripts / Config]

    B --> B1[docs/databricks.md]
    B --> B2[preparation-python.md]
    B --> B3[preparation-scala.md]
    B --> B4[pca/README.md]
    B --> B5[tpcds/README.md]
    B --> B6[UDF README.md]
    B --> B7[spark-connect README.md]
    B --> B8[Optuna README.md]
    B --> B9[tools/databricks README.md]

    C --> C1[optuna-dataframe.ipynb]
    C --> C2[pca.ipynb]
    C --> C3[micro-benchmarks-gpu.ipynb]
    C --> C4[TPCDS-SF10.ipynb]
    C --> C5[MortgageETL.ipynb / mortgage-ETL.ipynb]
    C --> C6[taxi-ETL.ipynb × 2]

    D --> D1[init.sh / init_optuna.sh]
    D --> D2[start_cluster.sh]
    D --> D3[extract-cudf-libs.sh]
    D --> D4[pom.xml]
    D --> D5[docker-compose.yaml]

Loading

_{Reviews (2): Last reviewed commit: "Update examples/ML+DL-Examples/Spark-Rap..." | Re-trigger Greptile}

[greptile-apps]

Unexplained modification to cached notebook output

The subsample value in a pre-stored trial log output from December 2024 changed from 0.6312602499862605 to 0.6312606499862605 — a difference in the 7th decimal place. This historical output line is unrelated to the version bump and appears to be an accidental edit. Modifying stored outputs without re-running the notebook makes the notebook's recorded results inconsistent with what was actually computed.

[NvTimLiu]

LGTM, +1

Please check the greptile review thread

[NvTimLiu]

LGTM, +1

Please check the greptile review thread