Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16090
Yeah I was wondering if we should also try to fix that. It seems maybe not
as bad since unpartitioned tables usually aren't that big.
We can create separate tickets for investigating that, and also the
duplicate file scan issue (that might not be a regression).
On Sun, Dec 4, 2016, 12:05 AM Wenchen Fan <notificati...@github.com> wrote:
> After looking more at the code, now I agree with your approach. One
> question, seems we still scan the files when creating a unpartitioned
> external data source table?
>
> â
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/16090#issuecomment-264690256>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAA6Ska3bJklmhoUUWIaS1Tlg0ha1JsHks5rEnRigaJpZM4LA1GX>
> .
>
---
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
