You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/11/14 19:11:00 UTC
[jira] [Assigned] (SPARK-26065) Change query hint from a
`LogicalPlan` to a field
[ https://issues.apache.org/jira/browse/SPARK-26065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-26065:
------------------------------------
Assignee: Apache Spark
> Change query hint from a `LogicalPlan` to a field
> -------------------------------------------------
>
> Key: SPARK-26065
> URL: https://issues.apache.org/jira/browse/SPARK-26065
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.4.0
> Reporter: Maryann Xue
> Assignee: Apache Spark
> Priority: Major
>
> The existing query hint implementation relies on a logical plan node {{ResolvedHint}} to store query hints in logical plans, and on {{Statistics}} in physical plans. Since {{ResolvedHint}} is not really a logical operator and can break the pattern matching for existing and future optimization rules, it is a issue to the Optimizer as the old {{AnalysisBarrier}} to the Analyzer.
> Given the fact that all our query hints are either 1) a join hint, i.e., broadcast hint; or 2) a re-partition hint, which is indeed an operator, we only need to add a hint field on the {{Join}} plan and that will be a good enough solution for current hint usage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org