zhengruifeng commented on code in PR #48791: URL: https://github.com/apache/spark/pull/48791#discussion_r1908683079
########## sql/connect/common/src/main/protobuf/spark/connect/ml_common.proto: ########## @@ -0,0 +1,107 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +syntax = 'proto3'; + +package spark.connect; + +import "spark/connect/expressions.proto"; + +option java_multiple_files = true; +option java_package = "org.apache.spark.connect.proto"; + +// MlParams stores param settings for ML Estimator / Transformer / Evaluator +message MlParams { + // User-supplied params + map<string, Param> params = 1; +} + +// Represents the parameter type of the ML instance, or the returned value +// of the attribute +message Param { + oneof param_type { + Expression.Literal literal = 1; + Vector vector = 2; Review Comment: I also think we can optimize out the `message Param`: option 1: support `Vector` and `Matrix` in `message Literal`; option 2 (Preferred): Using `message Expression` or `Expression.Literal.Struct` to express the parameters; -- 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]
