Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-214131130
Close this for now and, if needed, I'll reopen this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user maropu closed the pull request at:
https://github.com/apache/spark/pull/10523
---
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 ena
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-169637852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-169602906
**[Test build #48927 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48927/consoleFull)**
for PR 10523 at commit
[`98c7af9`](https://gi
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-169284609
@yhuai yes and it's a pg-specific thing. I agree that we add it as a data
source option instead of sql conf. If the fix is acceptable, I'll fix this pr
to add a data sou
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-169221842
Is it a postgresql specific thing? Maybe it is better to allow users to set
a conf in the data source optionsS (a conf that can be set by doing
`sqlContext.read.option(ke
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-169215749
@yhuai Ah..., I misunderstood. Okay and how about turning on/off case
sensitivity in configurations, e.g., `spark.sql.jdbc.caseSensitivity`?
---
If your project is set
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-169210269
@maropu Let me explain. The case sensitivity in spark sql is actually
configurable. For HiveContext, we use case insensitive resolution.
---
If your project is set up fo
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-169193276
@yhuai Yes, quoted tables in postgres are always case-sensitive. We need to
support case-insensitive table names? Table names in sparksql
(`DataFrame#registerTempTable`)
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-169169290
@maropu Thank you for the PR. So, when you quote a table name in postgres,
the name is case-sensitive, right? Looks like we are always quoting the table
name? If so, seem
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168932900
@liancheng @yhuai Could you review this?
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168925983
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168925981
Merged build finished. Test PASSed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168925603
**[Test build #48734 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48734/consoleFull)**
for PR 10523 at commit
[`a6e3a73`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168904847
**[Test build #48734 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48734/consoleFull)**
for PR 10523 at commit
[`a6e3a73`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168897746
Merged build finished. Test FAILed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168897748
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168897724
**[Test build #48730 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48730/consoleFull)**
for PR 10523 at commit
[`f5537e9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168896889
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168896887
Build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168895627
**[Test build #48730 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48730/consoleFull)**
for PR 10523 at commit
[`f5537e9`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168883338
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168883335
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168883303
**[Test build #48723 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48723/consoleFull)**
for PR 10523 at commit
[`ba0e434`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168882985
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168882981
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168882881
**[Test build #48725 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48725/consoleFull)**
for PR 10523 at commit
[`ba0e434`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168879471
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168879469
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168879422
**[Test build #48725 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48725/consoleFull)**
for PR 10523 at commit
[`ba0e434`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168878696
**[Test build #48723 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48723/consoleFull)**
for PR 10523 at commit
[`ba0e434`](https://gi
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168878437
retest 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 this fea
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168869051
**[Test build #48703 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48703/consoleFull)**
for PR 10523 at commit
[`d261683`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168869192
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168869190
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168863041
**[Test build #48703 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48703/consoleFull)**
for PR 10523 at commit
[`d261683`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168013557
Merged build finished. Test FAILed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168013558
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168013529
**[Test build #48482 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48482/consoleFull)**
for PR 10523 at commit
[`65c048c`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168011707
**[Test build #48482 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48482/consoleFull)**
for PR 10523 at commit
[`65c048c`](https://gi
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-168009223
retest 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 this fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-167955853
Merged build finished. Test FAILed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-167955854
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
GitHub user maropu opened a pull request:
https://github.com/apache/spark/pull/10523
[SPARK-12581][SQL] Support case-sensitive table names in postgresql
Table names in postgresql is originally case-insensitive.
To support case-sensitive table names, we need to wrap names in doubl
44 matches
Mail list logo
