wenfang6 commented on issue #9965:
URL:
https://github.com/apache/incubator-gluten/issues/9965#issuecomment-2995095474
It works successfully with Spark 3.2.1. I think that Spark 3.2.1 and Spark
3.5.4 generate different Velox plans for the same query. This inconsistency
appears to be the root cause of the issue
velox plan like this:
```
-- Project[2][expressions: (n2_2:INTEGER, hash_with_seed(42,"n0_0")),
(n2_3:INTEGER, "n0_0"), (n2_4:VARCHAR, "n0_1"), (n2_5:INTEGER, "n0_0")] ->
n2_2:INTEGER, n2_3:INTEGER, n2_4:VARCHAR, n2_5:INTEGER
-- Filter[1][expression: and(isnotnull("n0_1"),equalto("n0_1","wukong"))]
-> n0_0:INTEGER, n0_1:VARCHAR
-- TableScan[0][table: hive_table] -> n0_0:INTEGER, n0_1:VARCHAR
--Project[4][expressions: (n4_4:INTEGER, "n0_0"), (n4_5:VARCHAR, "n0_1"),
(n4_6:INTEGER, "rk_11")] -> n4_4:INTEGER, n4_5:VARCHAR, n4_6:INTEGER
-- Filter[3][expression: equalto("rk_11",1)] -> n0_0:INTEGER,
n0_1:VARCHAR, n0_2:INTEGER, rk_11:INTEGER
-- Window[2][STREAMING partition by [n0_2] order by [n0_1 DESC NULLS
LAST] rk_11 := row_number() ROWS between UNBOUNDED PRECEDING and CURRENT ROW]
-> n0_0:INTEGER, n0_1:VARCHAR, n0_2:INTEGER, rk_11:INTEGER
-- OrderBy[1][n0_2 ASC NULLS FIRST, n0_1 DESC NULLS LAST] ->
n0_0:INTEGER, n0_1:VARCHAR, n0_2:INTEGER
-- ValueStream[0][] -> n0_0:INTEGER, n0_1:VARCHAR, n0_2:INTEGER
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
