GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/6396
[SPARK-7853] [SQL] Fix bug of class loader issue in Spark SQL
```
bin/spark-sql --jars
./sql/hive/src/test/resources/hive-hcatalog-core-0.13.1.jar
CREATE TABLE t1(a string, b string)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105261276
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105261356
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105262292
[Test build #33472 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33472/consoleFull)
for PR 6396 at commit
[`7bc8502`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105267397
[Test build #33472 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33472/consoleFull)
for PR 6396 at commit
[`7bc8502`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105267432
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105267434
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105533963
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105533925
Merged build triggered.
---
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105534216
[Test build #33516 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33516/consoleFull)
for PR 6396 at commit
[`dd78775`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105534604
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105534596
[Test build #33516 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33516/consoleFull)
for PR 6396 at commit
[`dd78775`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105534606
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105564950
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105564992
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105566020
[Test build #33520 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33520/consoleFull)
for PR 6396 at commit
[`fd26533`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105587044
[Test build #33520 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33520/consoleFull)
for PR 6396 at commit
[`fd26533`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105587064
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105587065
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105678308
@marmbrus @yhuai @liancheng
---
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105710990
@chenghao-intel We will submit a pr based on yours later.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-105712144
sure, I am also working on this now, hopefully we can solve that asap.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-107001622
This has been fixed right? If yes, can we close 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 you
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6396#issuecomment-107112936
oh, yes, closing it.
---
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 chenghao-intel closed the pull request at:
https://github.com/apache/spark/pull/6396
---
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
25 matches
Mail list logo
