Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: verifyTopicOnStartup field true as default #162

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

kutay-o
Copy link
Contributor

@kutay-o kutay-o commented Jan 2, 2025

The verification process helps you identify any problem about the topics. It was an optional feature, the clients should enable when creating consumer. If the clients forget to enable the feature, it is hard to identify the topic problems.

This pr introduce to enable main and retry topics verification process by default.

During application startup, topic verification validates whether the topics specified in the configuration exist in the Kafka brokers. If any topic is not present in the brokers, it raises an error.

Related to: #152

@kutay-o kutay-o force-pushed the feature/enable-topic-verification-by-default branch from f7e72fc to 99b6c73 Compare January 2, 2025 13:42
@kutay-o kutay-o changed the title Remove VerifyTopicOnStartUp flag and enable topic verify by default Verify main and retry topics by default Jan 2, 2025
@kutay-o kutay-o force-pushed the feature/enable-topic-verification-by-default branch from 99b6c73 to 9327066 Compare January 2, 2025 15:30
@kutay-o kutay-o force-pushed the feature/enable-topic-verification-by-default branch from 9327066 to a183a9f Compare January 7, 2025 06:20
@Abdulsametileri Abdulsametileri changed the title Verify main and retry topics by default feat: verifyTopicOnStartup field true as default Jan 7, 2025
@Abdulsametileri Abdulsametileri merged commit faa822e into v2 Jan 7, 2025
5 checks passed
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.

2 participants