Skip to content

Comments

(feat): Add support for timestamp datafusion pushdown#1968

Closed
frisbeeman wants to merge 1 commit intoapache:mainfrom
icegatetech:frisbeeman/pushdown-datafusion-timestamp
Closed

(feat): Add support for timestamp datafusion pushdown#1968
frisbeeman wants to merge 1 commit intoapache:mainfrom
icegatetech:frisbeeman/pushdown-datafusion-timestamp

Conversation

@frisbeeman
Copy link

Which issue does this PR close?

What changes are included in this PR?

DataFusion can push down expressions containing timestamp literals, but the current predicate mapping implementation doesn't support them. This PR adds support for timestamp literals with varying precision levels (nanoseconds from SQL engine, configurable precision from DataFrame API).

Are these changes tested?

Yes, unit tests are included in this PR.

@frisbeeman frisbeeman force-pushed the frisbeeman/pushdown-datafusion-timestamp branch from 899af98 to ef5bc75 Compare December 28, 2025 13:46
@frisbeeman frisbeeman force-pushed the frisbeeman/pushdown-datafusion-timestamp branch from ef5bc75 to 6946f31 Compare December 29, 2025 13:48
@frisbeeman
Copy link
Author

Waiting for decision about #1569, if it will be merged, I'll decline this PR

@frisbeeman frisbeeman marked this pull request as draft December 29, 2025 15:46
@frisbeeman frisbeeman force-pushed the frisbeeman/pushdown-datafusion-timestamp branch from 6946f31 to 8d3338a Compare February 9, 2026 20:12
@frisbeeman
Copy link
Author

#2069 fixed here

@frisbeeman frisbeeman closed this Feb 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No pushdown filters applied if temporal type was optimized into timestamp type by datafusion

3 participants