Uh oh!
There was an error while loading. Please reload this page.
[SPARK-2890][SQL] Allow reading of data when case insensitive resolution could cause possible ambiguity. - #2209
[SPARK-2890][SQL] Allow reading of data when case insensitive resolution could cause possible ambiguity.#2209marmbrus wants to merge 2 commits into
Conversation
SparkQA
commented
Aug 29, 2014
QA tests have started for PR 2209 at commit
|
SparkQA
commented
Aug 29, 2014
QA tests have finished for PR 2209 at commit
|
yhuai
commented
Aug 30, 2014
Reading parquet files in |
There was a problem hiding this comment.
Provide more information on which column (with the original column name) we will keep in the lowerCaseSchema?
marmbrus
commented
Aug 31, 2014
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 get rid of this check entirely. We can throw an error when your query is invalid, but throwing an exception just because at some point in a query something could be ambiguous seems overly restrictive. |
yhuai
commented
Aug 31, 2014
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 exception. |
SparkQA
commented
Sep 5, 2014
QA tests have started for PR 2209 at commit
|
SparkQA
commented
Sep 6, 2014
Tests timed out after a configured wait of |
marmbrus
commented
Sep 10, 2014
Jenkins, test this please. |
There was a problem hiding this comment.
Ahh, this reorders the schema and breaks things. Props to @andyk.
SparkQA
commented
Sep 10, 2014
QA tests have started for PR 2209 at commit
|
SparkQA
commented
Sep 11, 2014
QA tests have finished for PR 2209 at commit
|
SparkQA
commented
Sep 11, 2014
QA tests have started for PR 2209 at commit
|
SparkQA
commented
Sep 11, 2014
QA tests have finished for PR 2209 at commit
|
a703ff4 to
729cca4CompareSparkQA
commented
Sep 13, 2014
QA tests have started for PR 2209 at commit
|
SparkQA
commented
Sep 13, 2014
Tests timed out after a configured wait of |
JoshRosen
commented
Sep 13, 2014
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 majority of the time is spent in certain Hive compatibility tests: |
marmbrus
commented
Sep 13, 2014
@JoshRosen I am hoping that #2164 will fix the test time outs. |
SparkQA
commented
Sep 13, 2014
QA tests have started for PR 2209 at commit
|
SparkQA
commented
Sep 14, 2014
QA tests have finished for PR 2209 at commit
|
marmbrus
commented
Sep 16, 2014
Merged to master. Thanks for looking this over! |
Throwing an error in the constructor makes it possible to run queries, even when there is no actual ambiguity. Remove this check in favor of throwing an error in analysis when they query is actually is ambiguous.
Also took the opportunity to add test cases that would have caught a subtle bug in my first attempt at fixing this and refactor some other test code.