opensearch-project / opensearch-project/data-prepper
[Idea] Data Prepper can reload pipeline configuration without restarting
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
Changing any part of the data prepper pipeline configuration requires restarting the entire data prepper node / cluster. This creates downtime for the service.
Describe the solution you'd like
Data Prepper does not require reloading for updates to processors, sink configurations or to add a new node to a cluster.
Describe alternatives you've considered (Optional)
- A separate endpoint to update configurations
Additional context
I am open to alternatives and other ideas to make the management of data prepper pipelines easier.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating pipeline configuration loading and lifecycle management in the Java codebase, then clarify the reload mechanism and its scope with maintainers. Done would mean pipeline configuration changes, including processors, sinks, or new nodes, can be applied without restarting the Data Prepper service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100