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

Implement Pipeline Runner #5429

Open
Tracked by #5415
MohammedAghil opened this issue Feb 10, 2025 · 0 comments · May be fixed by #5435
Open
Tracked by #5415

Implement Pipeline Runner #5429

MohammedAghil opened this issue Feb 10, 2025 · 0 comments · May be fixed by #5435
Assignees
Labels
maintenance Issues to help maintain the project, such as improving builds, testing, etc.

Comments

@MohammedAghil
Copy link
Contributor

Problem

At Present, the functionalities of running a pipeline is encapsulated inside Process Worker. While this provides encapsulation, it does not provide a way for a given thread such as in the case of Zero buffer to execute processors and publish to sinks in a synchronous way without having an instance of Process Worker itself which contains additional responsibilities such as shutting down process for pipeline.

Describe the solution you'd like

Implement a Pipeline Runner by moving the functionalities of to reading from buffer, executing processors and publishing to sinks from process worker to a Pipeline runner class, which can be used by process worker and other threads.

Additional context

Zero Buffer

@MohammedAghil MohammedAghil linked a pull request Feb 13, 2025 that will close this issue
3 tasks
@dlvenable dlvenable mentioned this issue Feb 18, 2025
2 tasks
@dlvenable dlvenable added maintenance Issues to help maintain the project, such as improving builds, testing, etc. and removed untriaged labels Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Issues to help maintain the project, such as improving builds, testing, etc.
Projects
Development

Successfully merging a pull request may close this issue.

2 participants