new adaptor to write messages to a `kafka` topic
Open
Nobody has claimed this yet.
DevX
Needs Priority
New Adaptor
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 41
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 12
Description
Re: Jembi-CDC use case where we catch FHIR errors and then post the failed bundles kafka topic for further analyssi
- Maybe we can use a free account here to set up a test environment: https://www.confluent.io/confluent-cloud/
- But Rory recommends also setting up a local cluster to test and make sure no issues (might be a little different than confluent-cloud)
Need to consider auth (but auth may not be required if this is all running locally - e.g., with Jembi use case)
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. First clarify the Kafka message format, authentication expectations, and whether both Confluent Cloud and a local cluster are required; done should include a defined adaptor scope and tests covering the intended environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, kafka
- Domain
- data-engineering, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100