[jira] [Updated] (SPARK-10429) MutableProjection should evaluate all expressions first and then update the mutable row
[
https://issues.apache.org/jira/browse/SPARK-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yin Huai updated SPARK-10429:
-
Assignee: Wenchen Fan
> MutableProjection should evaluate all expressions first and then update the
> mutable row
> ---
>
> Key: SPARK-10429
> URL: https://issues.apache.org/jira/browse/SPARK-10429
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
>Reporter: Yin Huai
>Assignee: Wenchen Fan
>Priority: Blocker
>
> Right now, SQL's mutable projection updates every value of the mutable
> project after it evaluates the corresponding expression. This makes the
> behavior of MutableProjection confusing and complicate the implementation of
> common aggregate functions like stddev because developers need to be aware
> that when evaluating {{i+1}}th expression of a mutable projection, {{i}}th
> slot of the mutable row has already been updated.
> A better behavior of MutableProjection will be that we evaluate all
> expressions first and then update all values of the mutable row.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-10429) MutableProjection should evaluate all expressions first and then update the mutable row
[
https://issues.apache.org/jira/browse/SPARK-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Armbrust updated SPARK-10429:
-
Target Version/s: 1.6.0
Fix Version/s: (was: 1.6.0)
> MutableProjection should evaluate all expressions first and then update the
> mutable row
> ---
>
> Key: SPARK-10429
> URL: https://issues.apache.org/jira/browse/SPARK-10429
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
>Reporter: Yin Huai
>Priority: Blocker
>
> Right now, SQL's mutable projection updates every value of the mutable
> project after it evaluates the corresponding expression. This makes the
> behavior of MutableProjection confusing and complicate the implementation of
> common aggregate functions like stddev because developers need to be aware
> that when evaluating {{i+1}}th expression of a mutable projection, {{i}}th
> slot of the mutable row has already been updated.
> A better behavior of MutableProjection will be that we evaluate all
> expressions first and then update all values of the mutable row.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-10429) MutableProjection should evaluate all expressions first and then update the mutable row
[
https://issues.apache.org/jira/browse/SPARK-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yin Huai updated SPARK-10429:
-
Issue Type: Sub-task (was: Improvement)
Parent: SPARK-4366
> MutableProjection should evaluate all expressions first and then update the
> mutable row
> ---
>
> Key: SPARK-10429
> URL: https://issues.apache.org/jira/browse/SPARK-10429
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
>Reporter: Yin Huai
>Priority: Blocker
> Fix For: 1.6.0
>
>
> Right now, SQL's mutable projection updates every value of the mutable
> project after it evaluates the corresponding expression. This makes the
> behavior of MutableProjection confusing and complicate the implementation of
> common aggregate functions like stddev because developers need to be aware
> that when evaluating {{i+1}}th expression of a mutable projection, {{i}}th
> slot of the mutable row has already been updated.
> A better behavior of MutableProjection will be that we evaluate all
> expressions first and then update all values of the mutable row.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
