Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14729
The PR https://github.com/apache/spark/pull/14781 is opened. This one will
be closed. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14729
Thanks!
---
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/14729
@hvanhovell Will submit a PR for Spark 2.0.
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14729
@viirya Yeah, a normal temporary table would be resolved as a LogicalPlan.
Analyze Table does not give us any benefit there.
However, you are also allowed to do this:
```sql
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/14729
@hvanhovell as I know, a temporary table will be resolved as arbitrary
logical plan, instead of `LeafNode` that the statistics of a query plan is
based on. I think it will cause problem, doesn't it?
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14729
@gatorsmile yeah, we should fix this issue for `2.0.1`.
@viirya we do not need to support all kinds of temporary tables. However,
you are allowed to create a temporary read only table
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/14729
@hvanhovell Not related to this PR. But I would like to ask that do we need
to support temporary tables in `ANALYZE TABLE`? Because temporary tables (and
views) are actually represented by logical
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14729
@hvanhovell In the current master branch, if we want to support In-Memory
cataloged tables, we need to support data source tables. You know,
`SimpleCatalogRelation` is converted to
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14729
@gatorsmile shouldn't we do this the other way around? And enable `Analyze
Table` for any table? That is the only way CBO can be used anywhere.
Temporary tables might be a bit more
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14729
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64143/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14729
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/14729
**[Test build #64143 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64143/consoleFull)**
for PR 14729 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14729
**[Test build #64143 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64143/consoleFull)**
for PR 14729 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14729
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14729
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64134/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14729
**[Test build #64134 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64134/consoleFull)**
for PR 14729 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14729
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14729
cc @hvanhovell @cloud-fan
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14729
**[Test build #64134 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64134/consoleFull)**
for PR 14729 at commit
19 matches
Mail list logo
