ramu11 commented on PR #28730:
URL: https://github.com/apache/camel/pull/28730#issuecomment-6545537752
Thanks @Croway for the review. I've pushed the updates in commit
`833647702ac6` on branch `CAMEL-24781`.
**Changes made:**
- Scoped the effective Kafka transactional ID by the owning Camel route ID
in exactly-once mode. This prevents separate producer instances belonging to
different routes but sharing the same Kafka endpoint from fencing each other.
- Clarified the transactional ID configuration requirements in the component
documentation, including stable route IDs and unique base IDs across runtime
instances.
- Updated the transaction synchronization, exactly-once metadata handling,
and streaming processor logic, with additional unit and integration test
coverage.
- Corrected the DLQ regression-test setup so both DLQ URI branches use
`maxRequestSize=1024`, ensuring the test exercises the intended
failed-DLQ-delivery and source-record replay scenario.
**Validation:**
Ran:
```bash
mvn -pl components/camel-kafka install \
-DskipTests=false \
-DskipITs=false
```
Result: **BUILD SUCCESS**
Relevant test results:
- `KafkaExactlyOnceRegressionIT`: 15 tests, 0 failures, 0 errors.
- `KafkaExactlyOnceReReviewIT`: 17 tests, 0 failures, 0 errors.
- `KafkaExactlyOnceIT`: 1 test, passed.
- `KafkaExactlyOnceRebalanceIT`: 1 test, passed.
- Unit test run: 42 tests, 0 failures, 0 errors.
The supplied review integration test was used for local validation and is
not included in the commit.
All changes are committed and pushed. Could you please take another look?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
