Skip to content

Commit

Permalink
docs: Elaborate on date range granularity match strict checks
Browse files Browse the repository at this point in the history
  • Loading branch information
paveltiunov authored Feb 20, 2025
1 parent 1203291 commit a5598dd
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions docs/pages/reference/data-model/pre-aggregations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1111,8 +1111,12 @@ refreshes.
### `allow_non_strict_date_range_match`

The `allow_non_strict_date_range_match` property can be used to allow queries to
match this pre-aggregation when using non-strict date ranges. This is useful
when using a visualization tools such as [Apache
match this pre-aggregation when using non-strict date ranges.
By default Cube checks if requested date range exactly matches pre-aggregation granularity.
For example if you're requesting half of a day or your date range filter is just one millisecond off for daily granularity pre-aggregation Cube would not use such a pre-aggregation by default.
Use this flag to lift this strict check.
This is useful
when using a visualization tools such as Tableau or [Apache
Superset][ref-config-downstream-superset] that use loose date ranges by default.

<CodeTabs>
Expand Down

0 comments on commit a5598dd

Please sign in to comment.