Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16090
I looked at avoiding the creation of a CatalogFileIndex, but the way table
resolution works right now, the only way is to create some sort of dummy file
index class that does not support scans. It's not clear to me that is any
better than just creating a CatalogFileIndex, which seems better than
incorrectly creating an InMemoryFileIndex.
---
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
