AngersZhuuuu commented on a change in pull request #30869:
URL: https://github.com/apache/spark/pull/30869#discussion_r546682520



##########
File path: 
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/avro/AvroFileFormat.scala
##########
@@ -0,0 +1,49 @@
+/*
+ * 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.execution.datasources.avro
+
+import org.apache.avro.SchemaParseException
+
+object AvroFileFormat {

Review comment:
       > We need a bit more refactor here. avro data source is implemented in 
an external module and it's weird to put `AvroFileFormat` in sql/core. Can we 
add an API to `trait FileFormat` to do this check?
   
   Yea, I know that there is a `AvroFileFormat` in exteral/avro, but we can't 
reference it in DDLUtils. We can't add this API to `FileFormat` since Hive 
serde and Spark SQL FileFormat both need same check. 
   
   Orc and Parquet have same situation, maybe that's why they use 
`ParquetSchemaConverter.checkFieldNames(colNames)` and ` 
OrcFileFormat.checkFieldNames(colNames)`




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