Github user xwu0226 closed the pull request at:
https://github.com/apache/spark/pull/12579
---
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 en
Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-218549665
@liancheng Thank you for the detail explanation!! Yeah. if the goal is to
make sure Spark SQL can handle the generated DDL, then, we need to miss some
hive features for
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-218379687
Hey @xwu0226, sorry that I didn't explain why I opened another PR for the
same issue, was in code rush for 2.0...
So one of the considerations for all the nat
Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-218238618
@srowen Yes, for datasource table. This PR also includes the work for hive
syntax DDL too. I see #12781 mentions that there will be followup PR taking
care of the hive
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-218192270
@xwu0226 I think this is superseded by
https://github.com/apache/spark/pull/12781 ?
---
If your project is set up for it, you can reply to this email and have your
repl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-216763938
Can one of the admins verify this patch?
---
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 p
Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-215303758
@yhuai @liancheng , I see PR
[#12734](https://github.com/apache/spark/pull/12734) takes care of the
PARTITIONED BY and CLUSTERED BY (with SORTED BY) clause for CTAS syn
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-214553367
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
Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-214472079
@liancheng Thanks for triggering the test! I am looking into the test
failure.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-214466178
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/12579#issuecomment-214465973
**[Test build #56899 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56899/consoleFull)**
for PR 12579 at commit
[`13e9775`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-214466180
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/12579#issuecomment-214420652
**[Test build #56899 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56899/consoleFull)**
for PR 12579 at commit
[`13e9775`](https://gi
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-214419087
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 this fe
Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/12579#issuecomment-213126393
@yhuai @andrewor14 Thanks!
---
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/12579#issuecomment-213032974
Can one of the admins verify this patch?
---
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 p
GitHub user xwu0226 opened a pull request:
https://github.com/apache/spark/pull/12579
[SPARK-14346][SQL] Show Create Table (Native)
This is a rebased version of
[#12132](https://github.com/apache/spark/pull/12132) and
[#12406](https://github.com/apache/spark/pull/12406)
##
Github user xwu0226 closed the pull request at:
https://github.com/apache/spark/pull/12406
---
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 en
Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/12406#issuecomment-212752759
Thanks @wangmiao1981 .
This happens again. all the commits after my last commits got pulled into
this PR. I need to close it and open a new PR. Will submit a ne
Github user wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/12406#issuecomment-212752658
@xwu0226 use git rebase upstream/master. Do not use git merge
upstream/master. I have the same issue before. git merge will add others'
commits to your PR. git reb
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12406#issuecomment-211491518
CC @yhuai @andrewor14 The PR is ready for review. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
21 matches
Mail list logo