Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15673
For large tables, the degraded performance should be considered a bug as
well.
How about this.
1) If direct sql is disabled, log a warning about degraded performance with
this flag and fall back to fetching all partitions.
2) If direct sql is enabled, crash with a message suggesting to disable
filesource partition management and report a bug.
That way, we will know if there are cases where metastore pruning fails
with direct sql enabled.
---
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
