LuciferYang opened a new pull request, #13089:
URL: https://github.com/apache/gluten/pull/13089

   ## What changes are proposed in this pull request?
   
   Two Spark 3.3 references that the earlier cleanup (#13003) missed, both a 
straightforward version/text update.
   
   - `tools/workload/benchmark_velox/initialize.ipynb` provisioned its 
benchmark cluster with Spark 3.3.1 (`wget` of `spark-3.3.1-bin-hadoop3.tgz`, 
the unpack/symlink, and the yarn-shuffle jar). Following the notebook end to 
end produced a Spark that Gluten no longer runs on. Bumped to 3.5.5, the 
well-tested supported version and the repo's default `sparkbundle.version`, and 
bumped the py4j on `PYTHONPATH` from `0.10.9.5` to `0.10.9.7` to match (Spark 
3.4 upgraded py4j; 3.5.x ships `0.10.9.7`).
   - `WriteFilesExecTransformer` carried a `// To be compatible with Spark 
3.3/3.4` comment; dropped the `3.3`, since 3.4 is now the minimum. The line 
right below it already notes Spark 3.5+ strips these fields via SPARK-43123, so 
the comment now reads 3.4-only, which is exactly the range that still needs the 
manual cleanup.
   
   The other remaining Spark 3.2/3.3 references (the bolt `Makefile` dead 
targets and an apparently-unused ClickHouse test fixture) need an owner 
decision and are filed as #13088 instead.
   
   ## How was this patch tested?
   
   The comment change is comment-only. The notebook change is a provisioning 
version-string bump that I could not execute (it drives a multi-node cluster 
over ssh); `spark-3.5.5-bin-hadoop3.tgz` and `spark-3.5.5-yarn-shuffle.jar` are 
published on the Apache archive, and the notebook JSON still parses.
   
   ## Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude claude-opus-5
   
   Related issue: #13003
   


-- 
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]

Reply via email to