Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16809
thanks, merging to 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73516/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
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/16809
**[Test build #73516 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73516/testReport)**
for PR 16809 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16809
**[Test build #73516 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73516/testReport)**
for PR 16809 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
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/16809
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73271/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16809
**[Test build #73271 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73271/testReport)**
for PR 16809 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16809
**[Test build #73271 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73271/testReport)**
for PR 16809 at commit
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16809
I just found refresh table related to table insertion when
`DataFrameWriter.saveAsTable` with overwrite mode, and `InsetIntoHiveTable`.
`InsertHadoopFsRelation` need to refresh table?
---
If
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16809
where do we refresh table for table insertion? will we fresh twice(table
and path)?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16809
thanks a lot! It seems that add a REFRESH command is to not modify the
default behavior. if user want to refresh, they call the command manually.
@gatorsmile @sameeragarwal @hvanhovell
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16809
Found the design doc:
https://docs.google.com/document/d/1h5SzfC5UsvIrRpeLNDKSMKrKJvohkkccFlXo-GBAwQQ/edit?ts=574f717f#
> An alternative is to support a new command REFRESH path that
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16809
@cloud-fan The new behavior looks reasonable to me, unless users are
expecting to keey the original cached data.
I went over the change history. I found @sameeragarwal did this in
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16809
This is a behavior change rather than a bug fix, but I think this new
behavior makes more sense. cc @gatorsmile to confirm.
---
If your project is set up for it, you can reply to this email and
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16809
cc @cloud-fan @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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
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/16809
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72419/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16809
**[Test build #72419 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72419/testReport)**
for PR 16809 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16809
**[Test build #72419 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72419/testReport)**
for PR 16809 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72410/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
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/16809
**[Test build #72410 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72410/testReport)**
for PR 16809 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16809
**[Test build #72410 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72410/testReport)**
for PR 16809 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72408/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
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/16809
**[Test build #72408 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72408/testReport)**
for PR 16809 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16809
**[Test build #72408 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72408/testReport)**
for PR 16809 at commit
28 matches
Mail list logo
