Github user budde commented on the issue:
https://github.com/apache/spark/pull/16797
> Can we write such schema (conflicting columns after lower-casing) into
metastore?
I think the scenario here would be that the metastore contains a single
lower-case column name that could resolve to multiple case-sesnitive column
names in the underlying Parquet file. This could've happened via the user
manually executing a ```CREATE TABE...``` query with an explicit schema. Since
the metastore itself isn't really defining expected behavior in this case I
think we can just consider this undefined behavior and return the first field
that matches alphabetically.
I don't think this is very likely to be a legitimate usecase, but it's good
to point out edge cases.
---
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
