Skip to content

Standardize deduplication API and error-handling contract#511

Open
sebastienviale wants to merge 4 commits intomichelin:mainfrom
sebastienviale:feature/add_dedup_without_processing_result
Open

Standardize deduplication API and error-handling contract#511
sebastienviale wants to merge 4 commits intomichelin:mainfrom
sebastienviale:feature/add_dedup_without_processing_result

Conversation

@sebastienviale
Copy link
Copy Markdown
Collaborator

This PR improves and standardizes the deduplication API documentation and usage patterns in DeduplicationUtils.

Key changes
Clarified and corrected documentation for all deduplication methods.
Explicitly distinguishes between:
*WithErrors methods returning KStream<String, ProcessingResult<V, V>>
non-error methods returning KStream<String, V>
Updated all usage examples to correctly wrap *WithErrors methods with TopologyErrorHandler.catchErrors(...).
Added missing examples for both variants (with and without error handling) across:
deduplication by key
key + value
predicate-based deduplication
header-based deduplication
Fixed inconsistencies in method usage and improved clarity of expected behavior.
Removed ambiguity around when and how to use error-handling wrappers.

@sebastienviale sebastienviale force-pushed the feature/add_dedup_without_processing_result branch from 451bc0e to f4dd2f5 Compare April 15, 2026 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant