Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16080
thanks for the review, merging to master/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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69535/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69535 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69535/consoleFull)**
for PR 16080 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16080
@cloud-fan True. That is not the `oldTableDef` fetched from the metastore.
LGTM pending test
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69535 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69535/consoleFull)**
for PR 16080 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69525/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69525 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69525/consoleFull)**
for PR 16080 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69525 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69525/consoleFull)**
for PR 16080 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16080
@gatorsmile , `alterTable` don't need to change, the `provider` is not in
table properties but still in the `CatalogTable.provider` field.
---
If your project is set up for it, you can reply to
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16080
The
[`alterTable`](https://github.com/cloud-fan/spark/blob/5ee6489cdd1c22a1071c4fb6c7e4c4af126c9d50/sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala#L533)
API in
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69465/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69465 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69465/consoleFull)**
for PR 16080 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69465 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69465/consoleFull)**
for PR 16080 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69459/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69459 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69459/consoleFull)**
for PR 16080 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69459 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69459/consoleFull)**
for PR 16080 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16080
I see. Will be careful in the future to not break the forward compatibility.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16080
We can have a test to check the table properties don't contain the entry,
can't we?
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16080
@rxin I'm afraid it's hard to write forward compatibility tests using unit
test, we may need an external test infrastructure(python scripts) to do this.
---
If your project is set up for it, you
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16080
In a lot of environments people run multiple Spark versions side by side.
That's always been a big strength of Spark.
---
If your project is set up for it, you can reply to this email and have your
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16080
We need to provide forward compatibility? That is pretty hard.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16080
We need a test case here.
---
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 mallman commented on the issue:
https://github.com/apache/spark/pull/16080
I built and tested this branch, and it resolves the issue I was having with
reading Spark 2.1 tables in earlier versions of Spark. Thanks!
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69406/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69406 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69406/consoleFull)**
for PR 16080 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16080
**[Test build #69406 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69406/consoleFull)**
for PR 16080 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16080
cc @rxin @yhuai @mallman
---
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
32 matches
Mail list logo
