Github user jamartinh commented on the issue:
https://github.com/apache/spark/pull/14638
My humble comment is simply that an external Hive table still is a Hive
Table, and as such it should be transparent for whichever user how to work
with it, even for spark users like me. The expectation is that a query from
such table yield the same results as if it where queried from Hive. I have
seen people worried about this.
That is, it is very unexpected querying a table from Hive and obtain
different result when queried from Spark.
I still consider this functionality as a neccesary feature in order to
maintain consistency with Hive engine, otherwise spark hive datasource
will slowly be diverging from Hive. I feel this should not be the case.
Best,
Jose
El 9 dic. 2016 23:42, "Dongjoon Hyun" <notificati...@github.com> escribió:
Now, I think we have been considered almost pros and cons here. Thank you
all for reviewing and giving opinions for this issue.
I value the committers' decision and feel the worry from @rxin
<https://github.com/rxin> , @gatorsmile <https://github.com/gatorsmile> ,
@cloud-fan <https://github.com/cloud-fan> .
The overall opinion seems to be it's not a proper Spark way for Spark
users, right?
â
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/apache/spark/pull/14638#issuecomment-266143334>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADbWs0ABWRHyV8H1ZB_PdK087bCSEN13ks5rGdlagaJpZM4Jj_em>
.
---
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
