Github user skliarpawlo commented on the issue:
https://github.com/apache/spark/pull/15717
@jiangxb1987 thanks for so quick response! I filed the issue:
https://issues.apache.org/jira/browse/SPARK-23525
---
-
To
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
Please file a JIRA issue if you think there is unexpected behavior.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.a
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
Can you also show the result of DESC TABLE before and after the command?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@sp
Github user skliarpawlo commented on the issue:
https://github.com/apache/spark/pull/15717
@jiangxb1987 any ideas why this still doesn't work for me in spark 2.2.0?
Sample code:
```
spark.sql("""
alter table test_table
change column metric metric string comme
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15717
Merging in master.
---
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 i
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@gatorsmile I've updated the PR description, 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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
@jiangxb1987 Could you update the PR description to reflect the new syntax?
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
LGTM
---
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 fe
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70129/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70129 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70129/consoleFull)**
for PR 15717 at commit
[`73c82fc`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70129 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70129/consoleFull)**
for PR 15717 at commit
[`73c82fc`](https://github.com/apache/spark/commit/7
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@gatorsmile @cloud-fan In fact that's mainly my fault, I should have
checked that the syntax is the same as that in HIVE. I'm working on this now.
Thank you!
---
If your project is set up for
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Sorry for the last minute comment. I did not realize it until I manually
run these test cases in Hive.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15717
LGTM, @gatorsmile for final sign-off
---
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
enab
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70089/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70089 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70089/consoleFull)**
for PR 15717 at commit
[`57934d4`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70089 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70089/consoleFull)**
for PR 15717 at commit
[`57934d4`](https://github.com/apache/spark/commit/5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70073/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70073 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70073/consoleFull)**
for PR 15717 at commit
[`a71683c`](https://github.com/apache/spark/commit/
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@gatorsmile Thank you for your suggestions! I'll update the code this
evening!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Could you please also add a test case when `spark.sql.caseSensitive` is on?
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Could you please add a test case for verifying the metadata field of the
column will not be lost after adding a comment? Thanks!
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70073 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70073/consoleFull)**
for PR 15717 at commit
[`a71683c`](https://github.com/apache/spark/commit/a
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15717
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 feature
enabled and wishes so
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70064/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70064 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70064/consoleFull)**
for PR 15717 at commit
[`a71683c`](https://github.com/apache/spark/commit/a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70016/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70016 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70016/consoleFull)**
for PR 15717 at commit
[`f49b0a0`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #70016 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70016/consoleFull)**
for PR 15717 at commit
[`f49b0a0`](https://github.com/apache/spark/commit/f
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69993/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #69993 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69993/consoleFull)**
for PR 15717 at commit
[`945aa28`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #69993 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69993/consoleFull)**
for PR 15717 at commit
[`945aa28`](https://github.com/apache/spark/commit/9
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15717
Why can't we remove `alterTableComment`? It seems that the implementations
are same, so we can make it a util function to map alter column comment action
to `alterTable` call.
---
If your projec
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@cloud-fan @gatorsmile Thank you for comments! Perhaps we should focus on
adding the `ALTER TABLE CHANGE COLUMN` statement, and only support change
column comments in this PR. The remaining issu
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15717
ok then the parser rule looks good to me, my only concern is the new APIs
in `ExternalCatalog`, I don't think they are necessary, @jiangxb1987 what's the
motivation you added them?
---
If your p
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15717
Those are super useful to add in the future.
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
https://issues.apache.org/jira/browse/SPARK-18727 is a related JIRA. If we
allow users to manually change the schema, do we need to follow what Hive does
now? ALTER TABLE ADD/REPLACE/CHANGE COLU
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
> The column change command will only modify Hive's metadata, and will not
modify data. Users should make sure the actual data layout of the
table/partition conforms with the metadata definition
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15717
hmmm, Hive only change the metadata not data? When will users need to do so?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69921/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #69921 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69921/consoleFull)**
for PR 15717 at commit
[`8c46704`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #69921 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69921/consoleFull)**
for PR 15717 at commit
[`8c46704`](https://github.com/apache/spark/commit/8
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@cloud-fan Could you explain more about the reason why we are not planning
to support changing columns? It seems that implementing these statements are
not very hard if we decide to follow the H
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15717
I don't think we will support changing column type/name/position/metadata
in the near future, shall we simplify the syntax for changing column comment?
cc @yhuai @hvanhovell
---
If your project
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69166/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #69166 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69166/consoleFull)**
for PR 15717 at commit
[`fc9339b`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #69166 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69166/consoleFull)**
for PR 15717 at commit
[`fc9339b`](https://github.com/apache/spark/commit/f
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
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 feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69162/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #69162 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69162/consoleFull)**
for PR 15717 at commit
[`fc9339b`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #69162 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69162/consoleFull)**
for PR 15717 at commit
[`fc9339b`](https://github.com/apache/spark/commit/f
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
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 this feature
enabled and wishes so, or if the
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@gatorsmile Sure I'm fine with that. 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 this fe
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
@rxin I see.
@jiangxb1987 Could we revisit this PR after we release Spark 2.1? Now, the
major focus is on the bug fixing.
---
If your project is set up for it, you can reply to this e
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15717
I would not.
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
@yhuai @rxin Are we still targeting this to 2.1?
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
@yhuai @rxin Are we still targeting this to 2.1?
---
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 thi
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
What happened if no any change is made? What is the behavior?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68988/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68988 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68988/consoleFull)**
for PR 15717 at commit
[`184a006`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68988 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68988/consoleFull)**
for PR 15717 at commit
[`184a006`](https://github.com/apache/spark/commit/1
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Let us first resolve the paser/syntax-related issues.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
How about the partition columns of partitioned Hive serde tables?
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Will review this PR tomorrow.
---
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 a
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@gatorsmile I've added tests ensure that it support data source tables,
please check when you have time, thank you!
---
If your project is set up for it, you can reply to this email and have yo
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68719/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68719 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68719/consoleFull)**
for PR 15717 at commit
[`855d520`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68719 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68719/consoleFull)**
for PR 15717 at commit
[`855d520`](https://github.com/apache/spark/commit/8
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
It should support data source tables, acturally perhaps I should add test
cases in `DDLSuite` for that - yes I'll add that this evening. Thank you!
---
If your project is set up for it, you can
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Another question about this PR: does it support data source tables?
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Will review this PR tonight. 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 this feature
ena
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
I prefer to doing `[CASCADE|RESTRICT]` in a separate PR. However, we still
need to add a test case to verify whether the behavior is following the default
`RESTRICT`.
---
If your project is set
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@gatorsmile Would you please have a look at this when you have time? Thank
you!
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68586/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68586 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68586/consoleFull)**
for PR 15717 at commit
[`fc316cd`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68586 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68586/consoleFull)**
for PR 15717 at commit
[`fc316cd`](https://github.com/apache/spark/commit/f
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@gatorsmile Thank you for clarify, will review the `ALTER TABLE CHANGE
COLUMN` statement today. BTW do you think we should add `[CASCADE|RESTRICT]` in
this PR?
---
If your project is set up fo
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
A basic question. Like Hive, we should not support `ALTER VIEW CHANGE
COLUMN`, right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68565/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68565 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68565/consoleFull)**
for PR 15717 at commit
[`7976462`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68565 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68565/consoleFull)**
for PR 15717 at commit
[`7976462`](https://github.com/apache/spark/commit/7
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15717
@gatorsmile I have been busy on other stuffs recently so no progress has
been made on this PR, I will try to find some time to make this PR pass all
unit cases this weekend. Thank you for lookin
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Any update on this PR?
---
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 wishe
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68335/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68335 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68335/consoleFull)**
for PR 15717 at commit
[`0097809`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68335 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68335/consoleFull)**
for PR 15717 at commit
[`0097809`](https://github.com/apache/spark/commit/0
1 - 100 of 112 matches
Mail list logo
