You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Andrew Lamb (Jira)" <ji...@apache.org> on 2021/04/26 13:32:03 UTC
[jira] [Commented] (ARROW-11622) [Rust] [DataFusion]
AggregateExpression name inconsistency
[ https://issues.apache.org/jira/browse/ARROW-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332382#comment-17332382 ]
Andrew Lamb commented on ARROW-11622:
-------------------------------------
Migrated to github: https://github.com/apache/arrow-datafusion/issues/178
> [Rust] [DataFusion] AggregateExpression name inconsistency
> ----------------------------------------------------------
>
> Key: ARROW-11622
> URL: https://issues.apache.org/jira/browse/ARROW-11622
> Project: Apache Arrow
> Issue Type: Bug
> Components: Rust - DataFusion
> Reporter: Andy Grove
> Priority: Major
>
> I have an aggregate query and the AggregateExpr has this name
> {code:java}
> SUM(l_extendedprice Multiply Int64(1)){code}
> This is hiding the fact that the expression has a CAST operation:
> {code:java}
> expr: BinaryExpr { left: Column { name: "l_extendedprice" }, op: Multiply, right: CastExpr { expr: Literal { value: Int64(1) }, cast_type: Float64 } }, nullable: true }{code}
> In Ballista, this causes a problem with serde because after a rountrip, the expression has a name that includes the CAST and this causes a schema mismatch.
> {code:java}
> SUM(l_extendedprice Multiply CAST(Int64(1) AS Float64)) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)