Implement filtering for imported data

[RobertJoonas]

Changes

This PR adds support for filtering by imported data. What we can or cannot filter by is limited by the imported schemas. Usually that means that the relation between different properties does not exist - e.g. we cannot filter by page and break down by source. That information doesn't exist. However, in some tables, there are several properties - e.g. imported_locations contains country, region and city propertis. That means that filtering by country and breaking down by city is possible.

Whenever filters are applied and imported data is included in the currently viewed period, we will display warning bubbles if a certain report is not able to include imported data:

Note that this does not mean that native data is excluded - the dashboard in the screenshot simply doesn't have any.

Tests

• Automated tests have been added

Changelog

• Entry has been added to changelog

Documentation

• Docs have been updated

Dark mode

• The UI has been tested both in dark and light mode

[macobo]

Q: Can you explain the business logic here?

I'm planning on moving business logic soonish so would need to understand this better.

[RobertJoonas]

The transform_filters function is used for:

1. dropping the redundant "is name pageview" filter which doesn't make sense it imported data
2. mapping an event:goal filter into either event:name or event:page

In the imported querying logic we need to map goals to name/page in two places:

1. deciding whether imported data can be included or not (i.e. schema_supports_query)
2. actually applying the filter

The general business logic with imported data is that we can query different properties in relation to each other (breakdown prop / filters) as long as they belong to the same imported_* table.

For example, when filtering by event:page==/blog and event:goal==Visit /blog, the query is supported and the data should be fetched from the imported_pages table.

Happy to clarify it more in depth if you have any more specific questions :)

[macobo]

Request: If we can merge this faster by splitting this into separate FE and BE PRs I'd appreciate that. Blocked on a large chunk of query/APIv2 work on these changes.

[RobertJoonas]

Request: If we can merge this faster by splitting this into separate FE and BE PRs I'd appreciate that. Blocked on a large chunk of query/APIv2 work on these changes.

I think we don't need to split it and can go ahead and merge it on Monday.