Skip to content

Conversation

@KSDaemon
Copy link
Member

@KSDaemon KSDaemon commented Jan 15, 2025

This fixes queries with time dimensions but without granularities that don't hit pre-aggregations having set allow_non_strict_date_range_match=true.

Check List

  • Tests have been run in packages where changes made if available
  • Linter has been run for changed code
  • Tests for the changes have been added if not covered yet
  • Docs have been added / updated if required

@KSDaemon KSDaemon requested a review from a team as a code owner January 15, 2025 16:44
@KSDaemon KSDaemon force-pushed the fix/allow_non_strict_date_range_match-regress branch 2 times, most recently from 6a6dfe9 to 62c542f Compare January 15, 2025 21:14
@KSDaemon KSDaemon force-pushed the fix/allow_non_strict_date_range_match-regress branch 5 times, most recently from b7f2688 to b46262d Compare January 27, 2025 18:49
@KSDaemon KSDaemon requested a review from a team as a code owner January 29, 2025 13:02
@KSDaemon KSDaemon force-pushed the fix/allow_non_strict_date_range_match-regress branch from d06be73 to a668184 Compare January 29, 2025 13:03
@KSDaemon KSDaemon force-pushed the fix/allow_non_strict_date_range_match-regress branch from a668184 to 7d49c3b Compare January 29, 2025 15:08
@KSDaemon KSDaemon force-pushed the fix/allow_non_strict_date_range_match-regress branch from 905e873 to 30fd1c1 Compare January 31, 2025 12:03
@KSDaemon KSDaemon force-pushed the fix/allow_non_strict_date_range_match-regress branch from 30fd1c1 to 7389556 Compare January 31, 2025 15:44
@KSDaemon KSDaemon merged commit eff0736 into master Feb 6, 2025
51 checks passed
@KSDaemon KSDaemon deleted the fix/allow_non_strict_date_range_match-regress branch February 6, 2025 20:40
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.

4 participants