fix: reconcile tz-aware and naive datetimes in ordering filters - #11943
Merged
anakin87 merged 1 commit intoJul 10, 2026
Merged
Conversation
|
@Otis0408 is attempting to deploy a commit to the deepset Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
anakin87
approved these changes
Jul 10, 2026
anakin87
left a comment
Member
There was a problem hiding this comment.
Makes sense to me.
Thank you!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Anyone who filters documents with an ordering operator (
>,>=,<,<=) where both the filter value and the document meta value aredatetimeobjects, but the two differ in timezone-awareness (one naive, one tz-aware), hits an uncaughtTypeError: can't compare offset-naive and offset-aware datetimes. Because the exception is not aFilterError, it propagates out ofdocument_matches_filter/DocumentStore.filter_documentsand aborts the entire query.The root cause is in
_prepare_ordering_comparisoninhaystack/utils/filters.py. The naive/aware reconciliation helper_ensure_both_dates_naive_or_awarewas only invoked inside theisinstance(value, str) or isinstance(filter_value, str)branch. When both operands arrive asdatetimeobjects (no string involved), that branch is skipped and the code falls through directly to the raw>/<comparison, raising. The string-date path already handles this awareness mismatch gracefully, so the behavior was inconsistent depending on whether a date came in as a string or adatetime.The fix moves the reconciliation out of the string-only branch so it runs whenever both operands are
datetimeinstances:Before:
After:
A focused regression test is added to
test/utils/test_filters.pycovering both the aware-filter/naive-doc and naive-filter/aware-doc directions; it fails on the pre-fix code with the TypeError and passes with the fix. A release note is included underreleasenotes/notes/.