[
https://issues.apache.org/jira/browse/SPARK-23580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617473#comment-16617473
]
Wenchen Fan edited comment on SPARK-23580 at 9/17/18 12:57 PM:
---------------------------------------------------------------
I'm re-targeting to `2.5.0`. There are more tickets coming: SafeProjection with
fallback, Predicate with fallback, Ordering with fallback, etc.
was (Author: cloud_fan):
I'm adding `2.5.0` as a target version. There are more tickets coming:
SafeProjection with fallback, Predicate with fallback, Ordering with fallback,
etc.
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
