Releases: line/decaton
v9.5.1
What's Changed
Important
Please read the upgrade guide in https://github.com/line/decaton/releases/tag/v9.0.0 carefully
Breaking Changes
New Features
Bug Fixes
- feat:call processingReturn/Completion to close even if task fails to process (#271)
Improvements
Other Changes
- Bump kafka dependency to 3.9.2 (#270)
- Fix shadow build failure (#272)
- NO-ISSUE Run shadowJar task before assemble (#273)
Full Changelog: v9.5.0...v9.5.1
v9.5.0
What's Changed
Important
Please read the upgrade guide in https://github.com/line/decaton/releases/tag/v9.0.0 carefully
Breaking Changes
New Features
- Make lingerMillis and capacity dynamic for BatchingProcessor (#268)
Bug Fixes
Improvements
Other Changes
- Use SubscriptionBuilder.properties() to set property supplier (#206)
Full Changelog: v9.4.0...v9.5.0
v9.4.0
What's Changed
Important
Please read the upgrade guide in https://github.com/line/decaton/releases/tag/v9.0.0 carefully
Breaking Changes
New Features
Support yaml partially (#262)
- Now you can pass YAML file to decaton with central dogma. See https://github.com/line/decaton/blob/v9.4.0/docs/dynamic-property-configuration.adoc.
How to Migrate Dynamic Property Configuration in JSON to one in YAML
It's optional. If you want to use YAML instead of JSON, you can migrate with these steps
- Create a YAML file from the JSON file, and store them to Central Dogma.
- Upgrade Decaton from 9.y.z to 9.4.0 and change your decaton processors to read the YAML file retrieved from Central Dogma instead of JSON.
Just changing file path that is passed toCentralDogmaPropertySupplieris enough. - (2) is completed, you can delete the unnecessary JSON files.
Note you should care inconsistency between JSON and YAML files until (2) is completed.
Bug Fixes
Improvements
Other Changes
Full Changelog: v9.3.0...v9.4.0
v9.3.0
Important
Please read the upgrade guide in https://github.com/line/decaton/releases/tag/v9.0.0 carefully
Breaking Changes
New Features
Allow build processors using kafka-clients Deserializer (#267)
ProcessorsBuilder#consumingnow have an overload that acceptskafka.common.serialization.Deserializer<T>, which can be used to deserialize tasks using topic, record headers and custom TaskMetadata extraction logic is not necessary
Support JSON schema for decaton processor properties used in central dogma (#263)
- See https://github.com/line/decaton/blob/v9.3.0/docs/dynamic-property-configuration.adoc#json-schema
Bug Fixes
Improvements
Other Changes
Full Changelog: v9.2.1...v9.3.0
v9.2.1
v9.2.0
Important
Please read the upgrade guide in https://github.com/line/decaton/releases/tag/v9.0.0 carefully
Breaking Changes
New Features
- Add a metric for v9 upgrade (#264)
- The new metric
decaton.records.consumedis helpful on v9 migration to check if all DecatonClient are producing with new format
- The new metric
Bug Fixes
- Fix CentralDogmaPropertySupplier#setValue (#257)
Improvements
Other Changes
v9.1.2
Important
Please read the upgrade guide in https://github.com/line/decaton/releases/tag/v9.0.0 carefully
Breaking Changes
New Features
Bug Fixes
- Fix decaton.processor.processed.time to measure task processing time (#253)
Improvements
Other Changes
- OSSRH is deprecated (#254)
v9.1.1
v9.1.0
9.0.1
Important
Please read the upgrade guide in https://github.com/line/decaton/releases/tag/v9.0.0 carefully
Breaking Changes
New Features
Bug Fixes
Improvements
- Lower log level of partition processor core creation, to be virtual thread friendly #245