Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16672
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/16672
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72746/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16672
**[Test build #72746 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72746/testReport)**
for PR 16672 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16672
The changes in this PR affects both read and write paths. Please update the
PR description and title. Thanks!
---
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/16672
Could you please add the test cases for the scenarios (of non pre existing
location) you explained above? Thanks!
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16672
**[Test build #72746 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72746/testReport)**
for PR 16672 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16672
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16672
ping @gatorsmile
---
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 windpiger commented on the issue:
https://github.com/apache/spark/pull/16672
@gatorsmile could you give some suggestion? thanks very much!
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16672
It seems to me following hive is safer, any other ideas?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16672
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/16672
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71898/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16672
**[Test build #71898 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71898/testReport)**
for PR 16672 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16672
**[Test build #71898 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71898/testReport)**
for PR 16672 at commit
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16672
If we create the location path when alter table by user A, maybe we use
user B to run the job which have no permission to write data to the location,
is't it also not friendly? Maybe throw an
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16672
In hive:
1. read a table with non-existing path, no exception and return 0 rows
2. read a table with non-permission path, throw runtime exception
```
FAILED: SemanticException
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16672
I'm wondering how hive read a table with non-existing path.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16672
I am not very sure whether we should follow Hive in this case. The path
might be wrong or no permission to create such a directory. Thus, it might be
more user friendly if they can get the error
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16672
I test it in hiveï¼alter table set location does not create the dir
ï¼when we insert data onï¼the dir createed
---
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/16672
We also need to add a test case for in-memory catalog. Maybe we can wait
until https://github.com/apache/spark/pull/16592 is resolved?
Actually, this fix is not right. We should create
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16672
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/16672
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71808/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16672
**[Test build #71808 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71808/testReport)**
for PR 16672 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16672
**[Test build #71808 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71808/testReport)**
for PR 16672 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16672
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/16672
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71803/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16672
**[Test build #71803 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71803/testReport)**
for PR 16672 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16672
**[Test build #71803 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71803/testReport)**
for PR 16672 at commit
28 matches
Mail list logo
