[
https://issues.apache.org/jira/browse/SPARK-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622359#comment-16622359
]
Hyukjin Kwon commented on SPARK-25469:
--------------------------------------
There's currently an issue which happened before
(http://apache-spark-developers-list.1001551.n3.nabble.com/Some-PRs-not-automatically-linked-to-JIRAs-td22067.html)
> Eval methods of Concat, Reverse and ElementAt should use pattern matching
> only once
> -----------------------------------------------------------------------------------
>
> Key: SPARK-25469
> URL: https://issues.apache.org/jira/browse/SPARK-25469
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.4.0, 3.0.0
> Reporter: Marek Novotny
> Priority: Major
>
> Pattern matching is utilized for each call of {{Concat.eval}},
> {{Reverse.nullSafeEval}} and {{ElementAt.nullSafeEval}} and thus for each
> record of a dataset. This could lead to a performance penalty when expression
> are executed in the interpreted mode. The goal of this ticket is to reduce
> usage of pattern matching within the mentioned "eval" methods.
--
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
