Uh oh!
There was an error while loading. Please reload this page.
[SPARK-12275][SQL] No plan for BroadcastHint in some condition - #10265
[SPARK-12275][SQL] No plan for BroadcastHint in some condition#10265yucai wants to merge 2 commits into
Conversation
zzcclp
commented
Dec 11, 2015
Hi, @yucai , my code is executed successfully with this pr. It's great. |
yucai
commented
Dec 11, 2015
@zzcclp Good to know :). |
chenghao-intel
commented
Dec 11, 2015
LGTM |
andrewor14
commented
Dec 11, 2015
ok to test. @yhuai can you verify? |
SparkQA
commented
Dec 11, 2015
Test build #47592 has finished for PR 10265 at commit
|
chenghao-intel
commented
Dec 12, 2015
The failure seems not related to this change. |
There was a problem hiding this comment.
This is quite obvious, apply method will only make the rules within the object BasicOperators applied, but the data source(Parquet) is an extended strategy defined in another object, planLater means to search the all of the strategies(including the extensions), which is make more sense. That's why it caused exception says No plan for BroadcastHint as apply(child) returns Nil.
yucai
commented
Dec 13, 2015
Weird, I find no difference for org.apache.spark.sql.sources.JsonHadoopFsRelationSuite#"test all data types - TimestampType" in Jekins's test report. And also, I tried both org.apache.spark.sql.sources.JsonHadoopFsRelationSuite and org.apache.spark.sql.DataFrameJoinSuite with the latest Spark upstream + my PR locally, no failure also. What's wrong :( ? Jekins, can you retest this please? |
yucai
commented
Dec 14, 2015
retest this please |
yucai
commented
Dec 14, 2015
@andrewor14 , @yhuai could you kindly help re-trigger testing? Much thanks! |
yhuai
commented
Dec 14, 2015
ok to test |
yhuai
commented
Dec 14, 2015
test this please |
yhuai
commented
Dec 14, 2015
LGTM pending jenkins |
yhuai
commented
Dec 14, 2015
When merge this, let's also merge it to branch 1.5, 1.6, and master. |
SparkQA
commented
Dec 14, 2015
Test build #47642 has finished for PR 10265 at commit
|
yhuai
commented
Dec 14, 2015
Thanks! Merging to 1.5, 1.6, and master. |
When SparkStrategies.BasicOperators's "case BroadcastHint(child) => apply(child)" is hit, it only recursively invokes BasicOperators.apply with this "child". It makes many strategies have no change to process this plan, which probably leads to "No plan" issue, so we use planLater to go through all strategies. https://issues.apache.org/jira/browse/SPARK-12275 Author: yucai <yucai.yu@intel.com> Closes#10265 from yucai/broadcast_hint. (cherry picked from commit ed87f6d) Signed-off-by: Yin Huai <yhuai@databricks.com>
yhuai
commented
Dec 14, 2015
@yucai can you create a 1.5 backport for this one? There was a conflict when I tried to merge it to branch 1.5. It will be good to have a pr for the backport and make sure all tests are good. Thanks! |
yucai
commented
Dec 14, 2015
@yhuai sure, I will do that ASAP. |
…backport backport apache#10265 to branch 1.5 When SparkStrategies.BasicOperators's "case BroadcastHint(child) => apply(child)" is hit, it only recursively invokes BasicOperators.apply with this "child". It makes many strategies have no change to process this plan, which probably leads to "No plan" issue, so we use planLater to go through all strategies. https://issues.apache.org/jira/browse/SPARK-12275
… backport backport #10265 to branch 1.5. When SparkStrategies.BasicOperators's "case BroadcastHint(child) => apply(child)" is hit, it only recursively invokes BasicOperators.apply with this "child". It makes many strategies have no change to process this plan, which probably leads to "No plan" issue, so we use planLater to go through all strategies. https://issues.apache.org/jira/browse/SPARK-12275 Author: yucai <yucai.yu@intel.com> Closes#10291 from yucai/backport_1.5_no_plan_for_broadcasthint and squashes the following commits: b09715c [yucai] [SPARK-12275][SQL] No plan for BroadcastHint in some condition - 1.5 backport
When SparkStrategies.BasicOperators's "case BroadcastHint(child) => apply(child)" is hit, it only recursively invokes BasicOperators.apply with this "child". It makes many strategies have no change to process this plan, which probably leads to "No plan" issue, so we use planLater to go through all strategies.
https://issues.apache.org/jira/browse/SPARK-12275