[
https://issues.apache.org/jira/browse/SPARK-26065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Li resolved SPARK-26065.
-----------------------------
Resolution: Fixed
Assignee: Maryann Xue
Fix Version/s: 3.0.0
> 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: Maryann Xue
> Priority: Major
> Fix For: 3.0.0
>
>
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
