10.4.21 Changelog
almost 4 years ago
We have another double feature this week as we skipped last week's update.
What's new
- Domains: To help larger teams manage complex datasets, we released a mechanism to create database and schema filtered groups that users can select to filter the UI by team, focus area, etc.
- SQL Rule run history: Access the full run history of SQL rules including how many rows were returned in the Custom Monitor detail view
Improvements and fixes
- Add Project filter support to notifications: You can now filter notifications by Project in addition to Datasets, Tables and Tags.
- Edit aggregation window for Field Health and Dimension Tracking Monitors: Added a daily aggregation option to improve support for tables with small volume changes when tracked on an hourly basis
- Resolved a Looker lineage bug: Fixed an issue that was causing certain Looker assets to not appear in the Pipelines lineage graph
- Resolved a notification routing bug with SQL Rules: Fixed an issue where SQL Rule notifications were not being sent as expected based on the Notification configuration
What's next
- Spark lineage: For our Spark customers, we're working on launching lineage which will allow you to map how queries interact to form lineage
- Field level lineage: We're working on a way to expose field level lineage in the UI to help with both field-specific investigations and field deprecation