zhangxinyao88 opened a new pull request, #59772:
URL: https://github.com/apache/spark/pull/59772

   ### What changes were proposed in this pull request?
   
   Use `functionsDesc` when looking up `SimpleMessageJavaTypes` in the 
SPARK-59112 case in `ProtobufSerdeSuite`.
   
   ### Why are the changes needed?
   
   `SimpleMessageJavaTypes` is declared in `functions_suite.proto`, but the 
test currently searches `serde_suite.desc`. Maven generates a separate 
descriptor for each proto file, so the test fails with 
`PROTOBUF_MESSAGE_NOT_FOUND`. SBT combines the descriptors and can hide the 
incorrect reference.
   
   The same failure appears in five consecutive completed Maven Java 21 builds, 
including [this run](https://github.com/apache/spark/actions/runs/39615280924). 
The test was added in [SPARK-59112 / PR 
#58413](https://github.com/apache/spark/pull/58413).
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. This corrects the descriptor used by an existing test.
   
   ### How was this patch tested?
   
   Maven with Java 21: reproduced the failure before the correction (7 tests 
passed, 1 failed), then reran the complete `ProtobufSerdeSuite` after the 
correction (all 8 tests passed). The 20-module Maven reactor completed 
successfully. Protobuf test-source Scalastyle also passed.
   
   ```sh
   ./build/mvn -pl connector/protobuf -am \
     -Dtest=NoSuchTest -Dsurefire.failIfNoSpecifiedTests=false \
     -DwildcardSuites=org.apache.spark.sql.protobuf.ProtobufSerdeSuite test
   ```
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: OpenAI Codex (GPT-6)
   
   


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