Backport: Add support for Dimension(...).grain(...) in where filter

[DevonFulcher]

Resolving: SL-631

Description

Due to MetricFlow's reliance on version 0.2.x of DSI, the updates to support Dimension(...).grain(...) need to be made to this branch as well. I just combined the work from these PRs into this one #156, #154, #152

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• This PR includes tests, or tests are not required/relevant for this PR
• I have run changie new to create a changelog entry

[linear]

SL-631 Where Clause & Group By Updates

At launch (tomorrow):

1. Group by is the same
2. Where clause for time dimensions: where="{{ TimeDimension('metric_time', 'DAY') > '2020-01-01'}}"
3. Where clause for categorical: where="{{ Dimension('customer__country') == 'US' }} "

Post launch we update where clause to do this

1. Where clause will support the same as the GROUP BY - group_by={{ [Dimension('metric_time').grain('day') }}"
2. Any time dimension will require grain at all times in the group by (AND WHERE)
3. Both TimeDimension() and Dimension() will be supported in both GROUP_BY and WHERE

We should discuss remove "Dimension" out of categorical (e..g, allow a user to do {{ 'customer__**country' }} rather than {{ Dimension('customer__**country') }}

[tlento]

This all seems fine to me, given my understanding of the changes and how the backport deployment works with core 1.6.x, but I'd like @QMalcolm to take a look to confirm this is backwards compatible with existing 1.6 installations. In particular, I think there are some changes to the where_filter_parser along with the file move here.

[QMalcolm]

I unfortunately don't think we can back port this. Core imports the WhereFilterParser, and this changes that import path. Core's import of DSI is ~=0.2.0 in dbt-core 1.6.0 through 1.6.5, if we backported and released this, all fresh installs of those versions would break.

[tlento]

I unfortunately don't think we can back port this. Core imports the WhereFilterParser, and this changes that import path. Core's import of DSI is ~=0.2.0 in dbt-core 1.6.0 through 1.6.5, if we backported and released this, all fresh installs of those versions would break.

Is that the only issue? If so, can we add an import alias to the backport then? We should be able to put in a module in the original location that imports this WhereFilterParser (or defines a WhereFilterParser class that wraps it, if there are API changes that need to be managed).

[QMalcolm]

@DevonFulcher brought up the idea of moving the where_filter_parser.py file back out for the backport in slack, also @tlento brought it in an above comment. Combing through these changes, and imports of dbt-semantic-interfaces in dbt-core, I think we can get away with this by doing so.

[tlento]

Yay! 🚢