Github user gatorsmile commented on a diff in the pull request:

    https://github.com/apache/spark/pull/18907#discussion_r132515261
  
    --- Diff: 
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/interface.scala
 ---
    @@ -412,6 +412,11 @@ case class CatalogRelation(
       assert(tableMeta.partitionSchema.sameType(partitionCols.toStructType))
       assert(tableMeta.dataSchema.sameType(dataCols.toStructType))
     
    +  // If table schema is empty, Spark will infer the schema at runtime, so 
we should mark this
    +  // relation as unresolved and wait it to be replaced by relation with 
actual schema, before
    +  // resolving parent plans.
    +  override lazy val resolved: Boolean = tableMeta.schema.nonEmpty
    --- End diff --
    
    
https://github.com/apache/spark/blob/master/sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala#L1894-L1923
    
    We have a test case. I also saw multiple related JIRAs. The users complain 
the table with zero column does not have a correct number of rows after 
`EXCEPT` and `INTERSECT`...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to