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

Allow stateful processors only in global config #16653

Closed

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Feb 26, 2020

Alternative solution to #16349.

Add a different registry for "stateful" processors, processors that would need to be closed. Use this registry only in global configurations, so processors registered in this registry can only be used in global configuration. Using these processors there is not such a problem because these processors are used during all the life of the beat.
Registry for "stateful" processors also include stateless processors.

If we also add the closers in #16349, we could allow the selective use of stateful processors also in dynamic configurations. This would be needed to support processors in modules.

(Any alternative naming proposal for the "stateful" methods is welcome)

@jsoriano jsoriano added the Team:Integrations Label for the Integrations team label Feb 26, 2020
@jsoriano jsoriano self-assigned this Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants