ayushi-agarwal opened a new issue, #8897:
URL: https://github.com/apache/incubator-gluten/issues/8897
### Backend
VL (Velox)
### Bug description
select * from store_sales where ss_list_price<0;
When this query is run, filter is not being pushed to scan resulting in
higher latency for the query.
Plan comes out to be on latest main today:
TableScan[0][table: hive_table, remaining filter:
(and(isnotnull("ss_list_price"),lessthan("ss_list_price",0)))] -> n0_0:INTEGER,
n0_1:INTEGER, n0_2:INTEGER, n0_3:INTEGER, n0_4:INTEGER, n0_5:INTEGER,
n0_6:INTEGER, n0_7:INTEGER, n0_8:BIGINT, n0_9:INTEGER, n0_10:DOUBLE,
n0_11:DOUBLE, n0_12:DOUBLE, n0_13:DOUBLE, n0_14:DOUBLE, n0_15:DOUBLE,
n0_16:DOUBLE, n0_17:DOUBLE, n0_18:DOUBLE, n0_19:DOUBLE, n0_20:DOUBLE,
n0_21:DOUBLE, n0_22:INTEGER
Input: 0 rows (0B, 0 batches), Raw Input: 85327543 rows (4.22GB), Output:
0 rows (0B, 0 batches), Cpu time: 10.87s, Wall time: 50.51s, Blocked wall time:
0ns, Peak memory: 132.29MB, Memory allocations: 25232, Threads: 1, Splits: 98,
CPU breakdown: B/I/O/F (74.47us/0ns/10.87s/28.52us)
Previously without this change
https://github.com/apache/incubator-gluten/issues/6666 it was coming like below
where the filter was being pushed as range fliter.
TableScan[0][table: hive_table, range filters: [(ss_list_price, DoubleRange:
(-inf, 0.000000) no nulls)]] -> n0_0:INTEGER, n0_1:INTEGER, n0_2:INTEGER,
n0_3:INTEGER, n0_4:INTEGER, n0_5:INTEGER, n0_6:INTEGER, n0_7:INTEGER,
n0_8:BIGINT, n0_9:INTEGER, n0_10:DOUBLE, n0_11:DOUBLE, n0_12:DOUBLE,
n0_13:DOUBLE, n0_14:DOUBLE, n0_15:DOUBLE, n0_16:DOUBLE, n0_17:DOUBLE,
n0_18:DOUBLE, n0_19:DOUBLE, n0_20:DOUBLE, n0_21:DOUBLE, n0_22:INTEGER
Input: 0 rows (0B, 0 batches), Output: 0 rows (0B, 0 batches), Cpu time:
1.36s, Blocked wall time: 0ns, Peak memory: 34.88KB, Memory allocations: 121,
Threads: 1, Splits: 98
@rui-mo Is this a known issue?
### Spark version
Spark-3.5.x
### Spark configurations
_No response_
### System information
_No response_
### Relevant logs
```bash
```
--
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]
