How to avoid duplicate writes in JHipster Kafka consumers on retry
Context JHipster’s entity sub‑generator creates a @KafkaListener that relies on Spring Kafka’s default error handling. When the listener throws an exception after a database write, the consumer may either skip the record, retry it, or commit the offset prematurely, leading to duplicate writes. Unresolved Decision The generated code does not include a dead‑le
jhipster