Releases: databrickslabs/overwatch
v0602
v0601
v05061
HOTFIX - for #278
Databricks accidentally published some "corrupted audit logs" meaning that there were multiple columns with the same name with the only difference being case. This is considered a bad schema and Overwatch had to take steps to make sure customers didn't get stuck when these audit logs appeared.
As of today, the Databricks PR to resolve this has already been merged and deployed to production. There are still a few days of audit logs that can cause Overwatch to fail on previous releases, so if you get the failure mentioned in #278, please do upgrade to this release or higher.
v0506
v0505
Bug Fixes
lookupWhen Optimizations Alpha release
THIS IS NOT A PRODUCTION RELEASE
This release should not be used to run the Overwatch pipeline but can be used to explore certain complex queries in progress for some specific users. When Issue 203 is merged and deployed these optimizations will be considered production-ready.
v0504
Hotfixes
v0503
FIXES INCLUDE:
- Incremental input sources returning 0 rows when users run Overwatch multiple times in the same day
- Incremental clusterStateFactGold -- addresses orphaned events for long-running states across Overwatch Runs.
- null driver node types for pooled drivers
- Improved instance pool lookup logic
- Mixed instance pools enabled
- basic refactoring for sparkOverrides -- full refactor in 0.5.1
- Improved logging
- Costing - node details lookups for edge cases -- there was a bug in the join condition for users running Overwatch multiple times per day in the same workspace
v0502
Missed a bug in 0501, re-releasing due to resolve.
v0501
Hotfixes