anishshri-db commented on code in PR #43961: URL: https://github.com/apache/spark/pull/43961#discussion_r1430857638
########## sql/api/src/main/scala/org/apache/spark/sql/streaming/StatefulProcessorHandle.scala: ########## @@ -0,0 +1,33 @@ +/* + * 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. + */ +package org.apache.spark.sql.streaming + +import java.io.Serializable + +import org.apache.spark.annotation.{Evolving, Experimental} + +/** + * Represents the operation handle provided to the stateful processor used in the + * arbitrary state API v2. + */ +@Experimental +@Evolving +trait StatefulProcessorHandle extends Serializable { + + /** Function to create new or return existing single value state variable of given type */ Review Comment: So within the same query, we expect different state vars to have different names. I'll probably add a check for this (might need to keep some local state within the handle) For the cluster, I don't think we have a restriction as such. Basically these are like logical partitions within the same RocksDB instance - so they are already scoped to that instance Based on the RocksDB doc I read so far, I don't think have come across any such limitation on the allowed chars -- 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]
