-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CORE] The fallback check for Scan should not be skipped when DPP is present #7078
Comments
it looks like a bug when enabling iceberg reader |
@zhztheplayer Thank you for the information provided. |
#6514 is a similar issue. This is a int64 timestamp, right? We can't get from the data type whether this is an int64 or an int96 timestamp. |
Backend
VL (Velox)
Bug description
Exception information
ERROR
Plan
Reason
BatchScan (34)
:RuntimeFilters: [dynamicpruningexpression(true)]
Filter (35)
: Vanilla filterThere is an unsupported
timestamp
type inBatchScan (34)
, which should normally trigger a fallback. However, when these conditions are met,BatchScan (34)
skips the fallback check.skip1
skip2
Spark version
Spark-3.3.x
Spark configurations
spark.gluten.sql.parquet.timestampType.scan.fallback.enabled=true
System information
No response
Relevant logs
No response
The text was updated successfully, but these errors were encountered: