You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2018/12/07 06:55:00 UTC
[jira] [Commented] (SPARK-23580) Interpreted mode fallback should
be implemented for all expressions & projections
[ https://issues.apache.org/jira/browse/SPARK-23580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712410#comment-16712410 ]
Dongjoon Hyun commented on SPARK-23580:
---------------------------------------
I removed the target version `2.5.0`. Please feel free to add `3.0.0` if needed.
> Interpreted mode fallback should be implemented for all expressions & projections
> ---------------------------------------------------------------------------------
>
> Key: SPARK-23580
> URL: https://issues.apache.org/jira/browse/SPARK-23580
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.3.0
> Reporter: Herman van Hovell
> Priority: Major
> Labels: release-notes
>
> Spark SQL currently does not support interpreted mode for all expressions and projections. This is a problem for scenario's where were code generation does not work, or blows past the JVM class limits. We currently cannot gracefully fallback.
> This ticket is an umbrella to fix this class of problem in Spark SQL. This work can be divided into two main area's:
> - Add interpreted versions for all dataset related expressions.
> - Add an interpreted version of {{GenerateUnsafeProjection}}.
--
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