advancedxy commented on code in PR #42255:
URL: https://github.com/apache/spark/pull/42255#discussion_r1280578680
##########
sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala:
##########
@@ -1407,7 +1407,15 @@ class Dataset[T] private[sql](
*/
@scala.annotation.varargs
def hint(name: String, parameters: Any*): Dataset[T] = withTypedPlan {
- UnresolvedHint(name, parameters, logicalPlan)
+ // parse string parameters into Expressions as ResolveHint requires all
the parameters to be
+ // expressions except the first one could be numeric. This logic matches
how sql hint is parsed
+ // and makes caller easier to pass string parameters in hint
specification, especially for
+ // other language bindings, such as PySpark.
+ val pars = parameters.map {
+ case s: String => sparkSession.sessionState.sqlParser.parseExpression(s)
Review Comment:
> This is too much breaking change. Previously the strings were literals and
now they are treated as columns.
It might not be too much breaking change. For all the supported hints, they
all requires the hint parameters to be `UnresolvedAttribute`, so if a string
literal is passed as parameter, the `ResolveHints` rule will throw analysis
exception anyway. Like I said in the comment, this behavior matches how `sql
hint` is parsed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
