GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/2209
[SPARK-2890][SQL] Allow reading of data when case insensitive resolution
could cause possible ambiguity.
You can merge this pull request into a Git repository by running:
$ git pull https://
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-53936431
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19498/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-53940609
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19498/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/a
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-53945691
Reading parquet files in `HiveContext` triggers the problem? If we have two
columns `c1, C1`, we will not be able to read `C1` when we are using case
insensitive resolution
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/2209#discussion_r16927258
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicOperators.scala
---
@@ -158,11 +159,18 @@ case class Subquery(alias: Str
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-53975089
I actually encountered the error with a jsonRDD, but yeah it could happen
with parquet files as well. Your comment about joins though makes me think
that we should just
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-53975391
Sounds good. I was not sure how to correctly query those results with
ambiguous schemas when I added that check. Seems an more informative logging
entry is better than an e
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-54695039
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19848/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-54699191
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19848/consoleFull)**
after a configured wait of `120m`.
---
If your project i
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55076950
Jenkins, test this please.
---
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
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/2209#discussion_r17380899
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicOperators.scala
---
@@ -158,11 +159,18 @@ case class Subquery(alias:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55201477
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/40/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55206184
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/40/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55218135
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/59/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55223584
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/59/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55506022
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/90/consoleFull)
for PR 2209 at commit
[`729cca4`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55509181
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/90/consoleFull)**
after a configured wait of `120m`.
---
If your project i
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55509238
Jenkins will actually show you how long the tests took, which can be
helpful in narrowing down why we're seeing these timeouts. In this case, it
looks like the majorit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55509530
@JoshRosen I am hoping that #2164 will fix the test time outs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55510444
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/99/consoleFull)
for PR 2209 at commit
[`729cca4`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55512344
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/99/consoleFull)
for PR 2209 at commit
[`729cca4`](https://github.com/a
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55792642
Merged to master. Thanks for looking this over!
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2209
---
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 enab
23 matches
Mail list logo
