justinmclean opened a new issue, #4700: URL: https://github.com/apache/iggy/issues/4700
### Description The sink data producer fills a topic with JSON records so a sink connector has something to read. Rust has one (`examples/rust/src/sink-data-producer/`) and so does Node. Python has none. ### Affected area / component Python examples ### Proposed solution Add `examples/python/sink-data-producer/producer.py` and a README section in `examples/python/README.md`. - Read `IGGY_STREAM` (default `qw`) and `IGGY_TOPIC` (default `records`), as the Rust version in `examples/rust/src/sink-data-producer/main.rs` does, and create the stream and topic if they are missing. - Match the Rust record fields, so the same connector config works for both. - Use the client set-up from the `high-level` or `basic` example. - Send the records as JSON and log a count when finished. - The Node version deletes the topic and stream when it finishes. Check what the Rust version does, follow it, and say which in the README. **How to test:** start a fresh server, run `uv run sink-data-producer/producer.py` from `examples/python`, and confirm the records poll back as valid JSON. ### Good first issue - [x] I think this could be a good first issue for a new contributor -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
