You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2016/02/05 22:14:39 UTC

[jira] [Commented] (SPARK-13215) Remove fallback in codegen

    [ https://issues.apache.org/jira/browse/SPARK-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135009#comment-15135009 ] 

Apache Spark commented on SPARK-13215:
--------------------------------------

User 'davies' has created a pull request for this issue:
https://github.com/apache/spark/pull/11097

> Remove fallback in codegen
> --------------------------
>
>                 Key: SPARK-13215
>                 URL: https://issues.apache.org/jira/browse/SPARK-13215
>             Project: Spark
>          Issue Type: Improvement
>            Reporter: Davies Liu
>
> in newMutableProjection, it will fallback to InterpretedMutableProjection if failed to compile.
> Since we remove the configuration for codegen, we are heavily reply on codegen (also TungstenAggregate require the generated MutableProjection to update UnsafeRow), should remove the fallback, which could make user confusing, see the discussion in SPARK-13116.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org