3.0.3

Breaking Changes

New Features

Bug Fixes

• Leave completion object in ProcessingContext field to avoid leak #124

Improvements

Other Changes

• Use toBuilder = true on config classes #122

3.0.2

Breaking Changes

New Features

Bug Fixes

• Use a single CentralDogma watcher per file (#121)

Improvements

Other Changes

3.0.1

Breaking Changes

New Features

Bug Fixes

• Properly shutdown subscription even when its closed without started (#116)

Improvements

Other Changes

3.0.0

This release contains a new feature called "deferred completion timeout" that can be used to prevent a decaton processor from stuck consumption permanently by leaking a DeferredCompletion, along with some breaking changes.

We haven't removed or marked deprecated a DefferredCompletion, but from this release you're recommended to use Completion interface instead of DeferredCompletion.

Please see the each PR's description for the detail of breaking change.

Breaking Changes

• Support deferred completion timeout as a workaround for "leak" (#99)
• default linger.ms 0 doesn't make sense typically (#108)

New Features

• Support deferred completion timeout as a workaround for "leak" (#99)

Bug Fixes

Improvements

• default linger.ms 0 doesn't make sense typically (#108)

Other Changes

• Upgrade micrometer to 1.6.6 (#106)
• Upgrade CentralDogma to 0.49.1, Jackson to 2.12.3 (#107)
• Support MDC enable/disable flag in BM for allocation profiling (#110)
• Correct outdated import paths in docs/example project (#111)
• Follow-up docs to update for latest APIs (#112)
• Correct package of Completion class as it's required to construct a processor (#113)

v2.1.0

Breaking Changes

New Features

• Make max.poll.records customizable through consumer properties (#105)

Bug Fixes

Improvements

• Reduce some object allocations that are identified as expensive by allocation profiling (#104)

Other Changes

v2.0.0

Breaking Changes

• Stop setting record timestamp from meta fixes (#102)
  • Regarding this fix, DecatonClient no longer propagates TaskMetadata#timestampMillis to ProducerRecord#timestamp. ProducerRecord#timestamp will be set to System.currentTimeMillis by KafkaProducer internally, regardless of TaskMetadata.

New Features

Bug Fixes

Improvements

Other Changes

• Add integration tests for BraveTracingProvider (#93)
• MetricsTest should clear metrics in advance to make test result stable (#95)

v1.1.0

Breaking Changes

New Features

• Wait for async tasks to finish in ProcessPipeline#close (#79)

Bug Fixes

Improvements

Other Changes

• Migrate to GitHub Actions (#90)
• Fix flaky and broken offsetRegression test (#91)
• Upgrade test dependencies (#92)

v1.0.2

Breaking Changes

New Features

Bug Fixes

• Bugfix: Exception from consumer.pause() in rebalance due to passing already revoked partition (#88)

Improvements

Other Changes

v1.0.1

Breaking Changes

New Features

Bug Fixes

• Fix regression handling (#86)

Improvements

Other Changes

• DocChecker: Fail validation only if base_version differs to the release version by major version (#87)

v1.0.0

This is the first Decaton major release 🎉
The 1.0.0 version contains no new big feature though. It is the version to state that Decaton has been confirmed as stable enough having long enough production experience with various services.
Starting from this version, we'll follow Semantic Versioning for future release versions as explained in VERSIONING.
By #83 , we have separated private APIs from the public APIs by package, so it contains breaking change requiring you to adjust your application code. Please see the Public APIs and be aware which resources are considered as a Public API.
Thanks always for your support!

Breaking Changes

• Separate internal-only APIs from public API by package (#83)

New Features

Bug Fixes

Improvements

• Add a workaround to build on arm64 mac (#76)
• ProcessorSubscription refactoring (#60)

Other Changes

• Add document explaining new versioning policy that is based on semantic versioning (#77)
• Use auto.offset.reset=earliest for benchmark (#81)
• Update VERSIONING doc following the recent public API separation (#84)
• Update release script to follow the new versioning scheme (#85)