Github user sameeragarwal commented on the pull request:
https://github.com/apache/spark/pull/13150#issuecomment-220734823
@Parth-Brahmbhatt this looks pretty good. However, given that hitting the
underlying filesystem directly can incur a lot of latency (especially in case
of S3), can you please conf protect this change (with a comment about the
potential performance issues)? Additionally, perhaps it might be nice to set
the conf to false by default to prevent silent regressions for existing queries
(especially if we're targeting this for 2.0).
---
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
