haiyangsun-db opened a new pull request, #58738: URL: https://github.com/apache/spark/pull/58738
### What changes were proposed in this pull request? This PR relocates the UDF worker protobuf definitions beneath `udf/worker/proto/src/main/protobuf/udf/worker/proto/` and updates their intra-proto imports to use the corresponding qualified paths. This follows the namespaced source layouts used by other Spark protobuf definitions, including: - [Spark Connect common.proto](https://github.com/apache/spark/blob/master/sql/connect/common/src/main/protobuf/spark/connect/common.proto) - [configuration schema](https://github.com/apache/spark/blob/master/common/config/src/main/protobuf/org/apache/spark/config/config_schema.proto) - [status store types](https://github.com/apache/spark/blob/master/core/src/main/protobuf/org/apache/spark/status/protobuf/store_types.proto) - [streaming state message](https://github.com/apache/spark/blob/master/sql/core/src/main/protobuf/org/apache/spark/sql/execution/streaming/StateMessage.proto) ### Why are the changes needed? The UDF worker definitions previously used generic bare import names such as `common.proto` and `udf_message.proto`. Relocating them establishes stable, qualified import paths, avoiding ambiguity if Spark protobuf sources are later collected, indexed, or compiled alongside definitions with similarly named files. The message definitions, generated Java package, and wire format are unchanged. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? - `protoc` compilation of the relocated UDF worker protobuf definitions. - `build/mvn -pl udf/worker/proto,udf/worker/grpc -am -DskipTests compile` - `build/mvn -pl udf/worker/grpc -am test` - UDF worker core: 59 tests passed. - UDF worker gRPC: 60 tests passed. ### Was this patch authored or co-authored using generative AI tooling? Yes. -- 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]
