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
The global transforms that belong to various tags (or when combining a Data Policy's transforms with the transforms defined in the Global Transforms) can be overlapping / can collide. We should think of the strategy we want to apply in this situation. Multiple options:
First one wins (this is determined by the order in which the tags are returned by the processing platform / data catalog) -> possible leads to unexpected / unwanted policies.
Merge (how?)
Strict mode -> refuse to generate a bare policy with global transforms and let the end user first remove the overlap.
The UI will be very helpful here: showing whether the GlobalTransform is compatible with the Data Policy, and if not, what the conflicts are.
The text was updated successfully, but these errors were encountered:
getstrmbot
changed the title
[PACE-23] Determine strategy for overlapping transforms in GlobalTransforms
[PACE-23] Determine strategy for overlapping transforms in GlobalTransforms / Data Policies
Nov 10, 2023
The global transforms that belong to various tags (or when combining a Data Policy's transforms with the transforms defined in the Global Transforms) can be overlapping / can collide. We should think of the strategy we want to apply in this situation. Multiple options:
The UI will be very helpful here: showing whether the GlobalTransform is compatible with the Data Policy, and if not, what the conflicts are.
From SyncLinear.com | PACE-23
The text was updated successfully, but these errors were encountered: