Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PACE-23] Determine strategy for overlapping transforms in GlobalTransforms / Data Policies #33

Open
getstrmbot opened this issue Nov 8, 2023 · 0 comments
Labels
linear Created by Linear-GitHub Sync

Comments

@getstrmbot
Copy link
Collaborator

getstrmbot commented Nov 8, 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:

  1. 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.
  2. Merge (how?)
  3. 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.

From SyncLinear.com | PACE-23

@getstrmbot 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
@trietsch trietsch added the linear Created by Linear-GitHub Sync label Nov 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
linear Created by Linear-GitHub Sync
Projects
None yet
Development

No branches or pull requests

2 participants