Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18189
cc @rxin @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 wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18189
**[Test build #77689 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77689/testReport)**
for PR 18189 at commit
[`3dea8e0`](https://github.com/apache/spark/commit/3d
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18189
**[Test build #77689 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77689/testReport)**
for PR 18189 at commit
[`3dea8e0`](https://github.com/apache/spark/commit/3
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18189
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18189
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77689/
Test PASSed.
---
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18189
cc @bogdanrdc
---
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
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/18189
tbh the difference is so small that i don't think it is worth spending time
here ... as pointed out it is not forceBroadcast either.
---
If your project is set up for it, you can reply to this email a
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18189
I found this problem when I was playing with CBO stuff. This
name(`isBroadcastable`) will be displayed with the query plan when users run
`EXPLAIN COST`, that's why I think it matters.
---
If yo
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/18189
But isn't it in a hint? If you are worried about user, I'd just change it
to "broadcast".
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18189
**[Test build #0 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/0/testReport)**
for PR 18189 at commit
[`3706ab2`](https://github.com/apache/spark/commit/37
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18189
**[Test build #0 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/0/testReport)**
for PR 18189 at commit
[`3706ab2`](https://github.com/apache/spark/commit/3
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18189
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/0/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18189
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
e
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18189
LGTM
---
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 featur
14 matches
Mail list logo
