You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix assertion bug in remote executor and update notes
Fixed a state management bug in the coordinator that caused assertions to stop running on remote workers. Updated known issues section to reflect the correct version for the fix.
Copy file name to clipboardExpand all lines: docs/managed-datahub/release-notes/v_0_3_15.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,9 @@ This contains detailed release notes, but there's also an [announcement blog pos
31
31
32
32
- Elasticsearch 7: Fix role creation
33
33
- Elasticsearch/Opensearch: Allow role to inspect nodes for query optimization
34
+
-**Assertions on remote executor**: There was a state management bug in the coordinator on `3.15-acryl` which caused assertions to stop running on remote workers. This infrastructure bug has been fixed and tested for to prevent future regressions.
35
+
36
+
34
37
35
38
### v0.3.15-acryl
36
39
@@ -67,6 +70,7 @@ Fixes:
67
70
68
71
## Known Issues
69
72
70
-
- Assertions do not run on remote executor deployment modes. Please look to 3.15.3 for the fix.
73
+
- Assertions do not run on remote executor deployment modes. Please look to 3.15.4 for the fix.
74
+
- There is some backward incompatibilities between older remote executors and 3.15 GMS. Remote executors may need to be upgraded to resolve these.
71
75
- PATCH of the Ownership aspect does not support assigning the same owner to multiple ownership type urns
72
76
- If you were to upgrade to v0.3.15 and create a "Platforms" home page module, in order to roll back to a previous version of DataHub you will need to either (1) remove the Platforms modules from all home page templates or (2) roll back to v0.3.14.2 which includes a fix to handle unknown module types. This sort of backwards compatibility with home page modules is resolved going forward with v0.3.15.
0 commit comments