rdblue commented on a change in pull request #24559:
URL: https://github.com/apache/spark/pull/24559#discussion_r605229535



##########
File path: 
sql/catalyst/src/main/java/org/apache/spark/sql/connector/catalog/functions/Function.java
##########
@@ -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.connector.catalog.functions;
+
+import java.io.Serializable;
+
+/**
+ * Base class for user-defined functions.
+ */
+public interface Function extends Serializable {
+
+  /**
+   * A name to identify this function. Implementations should provide a 
meaningful name, like the
+   * database and function name from the catalog.
+   */
+  String name();

Review comment:
       Not here because this is the name reported by the function for Spark to 
use in messages. Case sensitivity is a concern when loading. There, we can't 
change whether the catalog is case sensitive or not, so I'm not sure it would 
provide much value. If you think it does, then please follow up with a PR that 
adds some wording for the `TableCatalog` and `FunctionCatalog` interfaces.




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

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