Repository navigation
Expression handling in VortexSource isn't consistent, and might cause runtime errors or other issues. #8763
Description
The default behavior in can_be_pushed_down_impl treats CastExpr as supported only by the overall shape of the child, but doesn't validate its actual children.
For example WHERE CAST(a % 2 AS BIGINT) = 0 will be pushed down, but we currently can't handle %.
This is a symptom of a bigger drift between the different checks, conversions and operations like expression splitting.
Activity
haohuaijin commentedon Jul 31, 2026
I recently encounter this issue through the
ListingTable: DataFusion pushesCAST(Utf8 AS Int64) > 0into Vortex, which then fails at runtime withNo CastReduce to cast constant array from utf8 to i64?.And ListingTable currently provides no way to inject a custom
ExpressionConvertorto reject the unsupported pushdown.AdamGS commentedon Aug 4, 2026
The way in that case is passing a convertor through the underlying
VortexSource, depending on your setup.haohuaijin commentedon Aug 5, 2026
Thanks, but for users who use
ListingTableto search vortex files, configuringVortexSourcedirectly isn't straightforward becauseListingTablecreates sources throughVortexFormat. I opened #9185 to pass a customExpressionConvertorthroughVortexFormat/VortexFormatFactory.And publicly export
ProcessedProjection( because TheExpressionConvertortrait was already public, butsplit_projectionreturnsProcessedProjection, which was not publicly nameable — so the trait could not actually be implemented outside the crate).feat(datafusion): allow configuring `ExpressionConvertor` on `VortexF…