[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=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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[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=16617473#comment-16617473
]
Wenchen Fan commented on SPARK-23580:
-
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
[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=16610082#comment-16610082
]
Wenchen Fan commented on SPARK-23580:
-
There are still 2 open PRs, one is inactive for a while, one will be merged to
master soon. Shall we just move the inactive one out from this umbrella?
> 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
[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=16609787#comment-16609787
]
Reynold Xin commented on SPARK-23580:
-
90% or 100%?
> 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
[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=16609271#comment-16609271
]
Wenchen Fan commented on SPARK-23580:
-
Shall we resolve the ticket? It seems 90% done.
> 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
[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=16454918#comment-16454918
]
Bruce Robbins commented on SPARK-23580:
---
Should SortPrefix also get this treatment?
> 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
[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=16387315#comment-16387315
]
Takeshi Yamamuro commented on SPARK-23580:
--
I'll join this work, too.
> 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
>
> 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
[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=16386991#comment-16386991
]
Kazuaki Ishizaki commented on SPARK-23580:
--
Sure, I will work for them
> 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
>
> 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
[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=16386839#comment-16386839
]
Xiao Li commented on SPARK-23580:
-
cc [~kiszk] Could you help this umbrella ticket?
> 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
>
> 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
