Hello! When using exactly-once semantics, uncommitted or aborted records are skipped by the consumer as if they don't exist.
When inspecting the topic manually, use isolation.level=read_committed to get the same behavior. Ryanne On Fri, Mar 15, 2019, 6:08 AM Федор Чернилин <investorme...@gmail.com> wrote: > I also noticed another important thing now. Message which used for join is > uncommitted. I understood it with the help of consumer's setting isolation > level - read_committed. The message got into the topic using the same > stream app. Remind that stream app has processing guarantee > = exactly_once. How could this happen? >
