Github user OopsOutOfMemory closed the pull request at:
https://github.com/apache/spark/pull/4175
---
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 OopsOutOfMemory commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71577816
Thanks, squito :)
I'm working on this issue.
---
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 squito commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71577489
I think these failures are real, looks like you need to do a similar
updating of the args to `registerTempTable` in the pyspark tests, eg.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71589589
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71589586
[Test build #26141 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26141/consoleFull)
for PR 4175 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71583562
[Test build #26141 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26141/consoleFull)
for PR 4175 at commit
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71551408
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71552065
[Test build #26119 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26119/consoleFull)
for PR 4175 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71563629
[Test build #26119 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26119/consoleFull)
for PR 4175 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71563634
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71348013
Jenkins this is 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
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71348345
lets try this again ...
Jenkins this is 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
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71348093
this is mentioned in the jira, but its worth noting again here that this
changes the behavior slightly, since it wouldn't throw an exception before.
---
If your project
Github user OopsOutOfMemory commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71167869
/cc @scwf @chenghao-intel
---
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 OopsOutOfMemory opened a pull request:
https://github.com/apache/spark/pull/4175
[SPARK-3298][SQL] Add flag control overwrite registerAsTable /
registerTempTable
https://issues.apache.org/jira/browse/SPARK-3298
add a flag `allowOverwrite` to control
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71167100
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
Github user OopsOutOfMemory commented on the pull request:
https://github.com/apache/spark/pull/4175#issuecomment-71166995
@marmbrus Any comments 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
17 matches
Mail list logo
