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

Framework for deprecating pipeline functions; and deprecate remove_field #19287

Open
patrickmann opened this issue May 8, 2024 · 0 comments
Open
Labels

Comments

@patrickmann
Copy link
Contributor

Follow-up issue related to #19259, #19268

What?

  • A way to deprecate functions including making users aware of this in the UI.
  • Deprecate remove_field with the target of full removal in 7.0.
  • Add a rate-limited logger to RemoveField, signaling the deprecation.

Why?

Pipeline functions are like the GL API - we cannot easily introduce breaking changes or deprecate them, because it may cause existing functions to behave in unexpected ways; potentially even leading to data loss.
Breaking changes need to be communicated well ahead of time, in a way that is visible to users.

Case in point: #19259

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant