4
95%
master: 100%

Ran 06 May 2021 10:12AM UTC

Files 11

Run time 3s

Badge

Embed ▾

Committed 06 May 2021 09:57AM UTC coverage: 97.619% (-0.4%) from 98.068%

Job # RELEASE=true

Build Type

push

travis-ci-com

Committed by

web-flow

Commit Message

Allow the specification of the offset reset strategy (#26)

When no previous offset is present (because it is the first load) or the last offset gathered from the table is out of range (because the last load was longer ago than the topic retention time), the connector always starts from the end of topic (kafka default strategy 'latest'). For low throughput topics there might be no message at that point of time so again, no new offset is stored and the messages are lost. Additionally, for topics that work with compaction it is expected to load everything from beginning the topic.

This commit allows specifying `AUTO_OFFSET_RESET` as property and the value is passed to the kafka consumer.

Co-authored-by: Schulte, Johannes <johannes.schulte@eventim.de>
Co-authored-by: Muhammet Orazov <m.orazow@gmail.com>

Run Details

205 of 210 relevant lines covered (97.62%)

0.98 hits per line

exasol / kafka-connector-extension / 78 / 4
95%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 78.4 (RELEASE=true)

exasol / kafka-connector-extension / 78 / 4 95% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 78.4 (RELEASE=true)

exasol / kafka-connector-extension / 78 / 4
95%
master: 100%

README BADGES
x