Github user zuotingbing commented on the issue:
https://github.com/apache/spark/pull/17858
@gatorsmile it seems my mistake, i will try to fix 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 your project does
Github user zuotingbing commented on the issue:
https://github.com/apache/spark/pull/17858
@gatorsmile My production environment is spark 2.0.2 and test successful.
Is there something be changed since 2.0.2 for this case? Thanks!
---
If your project is set up for it, you can reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17858
**[Test build #76566 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76566/testReport)**
for PR 17858 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17858
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76566/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17858
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/17858
**[Test build #76566 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76566/testReport)**
for PR 17858 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17858
ok to test
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17858
This will not pass the test cases, because we only deleted the child
directory `.hive-staging` of the `stagingDir`
---
If your project is set up for it, you can reply to this email and have
Github user zuotingbing commented on the issue:
https://github.com/apache/spark/pull/17858
yes i tried the same thing in Hive, got the same error:
`2017-05-08T13:48:04,634 ERROR exec.Task (:()) - Failed with exception
Unable to move source
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17858
if this is a hive bug, this patch seems a valid workaround for Spark SQL.
---
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/17858
This sounds a bug in Hive metastore. Could you try the same thing in Hive?
Do you hit the same error? Let us see how Hive behaves and then we can decide
what is the best way to handle it.
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17858
Do you really need to force this? or, is it just that any path relative to
the output dir has to be a hidden directory starting with "." or "_"? For
example, right now this prevents me from making
Github user zuotingbing commented on the issue:
https://github.com/apache/spark/pull/17858
In this case, Hive will create the staging directory under the table
directory, and when moving staging directory to table directory, Hive will
still empty the table directory, but will exclude
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17858
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 project does not have this
14 matches
Mail list logo
