-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Redoer middleware #25
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
Conversation
43ab25c to
bcad121
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces a new "Redoer" middleware component that processes redo records from the Senzing engine in a continuous loop. The redoer retrieves and processes redo records, which are typically generated when entity resolution operations need to be reprocessed.
- Adds a new redoer middleware service with continuous record processing capabilities
- Integrates the redoer service into the Docker Compose configuration
- Updates documentation to include redoer usage instructions
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| middleware/redoer.py | Core redoer implementation with continuous loop for processing redo records |
| Dockerfile.redoer | Docker configuration for building the redoer service container |
| docker-compose.yaml | Adds redoer service configuration with database dependencies |
| README.md | Documents redoer service usage and command examples |
| middleware/consumer.py | Removes outdated TODO comment about DLQ logic |
| .trivyignore.yaml | Adds security exception for redoer Dockerfile |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
5606bd3 to
2b7b677
Compare
No description provided.