Github user OopsOutOfMemory closed the pull request at:
https://github.com/apache/spark/pull/4271
---
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/4271#issuecomment-82779677
OK,closed.
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-82687600
I propose we close this issue to keep the PR queue at a reasonable size.
If there if further discussion we can have it on the JIRA.
---
If your project is set up for
GitHub user OopsOutOfMemory opened a pull request:
https://github.com/apache/spark/pull/4271
[SPARK-3298][SQL] Add `allowExisting` flag to control registerAsTable /
registerTempTable
https://issues.apache.org/jira/browse/SPARK-3298
add a parameter into `registerTempTable`
Github user OopsOutOfMemory commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-72064637
@squito @marmbrus
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-72064796
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 squito commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-72083678
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/4271#issuecomment-72084211
[Test build #26328 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26328/consoleFull)
for PR 4271 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-72097975
[Test build #26328 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26328/consoleFull)
for PR 4271 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-72097991
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-72106118
I'm not entirely sure about this change as the semantics are kind of
confusing. Regardless, we should not change the existing behavior and break
all kinds of user
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-72099030
more real failures. Looks like you need to add that param in a few more
test cases still.
I will reiterate -- if we flip the default value, its no longer an api
12 matches
Mail list logo
