-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
add option to return error on non exiting topic for ConsumeTopics opt #439
Comments
So are you thinking an option to return all retryable errors in fetches, or just this one? |
does it possible to add option to handle all retryable errors so inside this func we can decide to continue retry or not? |
like |
The client already internally retries following roughly that exact pattern. For fetching, failed partitions are always retried forever. I thought you were asking for an option like,
such that that retryable errors here: Line 864 in 5379fb0
|
Internally, but if user wants to handle errors via own logic? One use-case - check that topic exists when subscribe to it. |
In that case, existence checking needs to be done before subscribing to it. However, with the option, you could react to errors (such as a topic being deleted). Would the option above satisfy what you're looking for? |
For when you want to return retryable errors to the client. Closes #439.
sometimes someone =) specify invalid topic name (non exiting), but kgo does not fails on subscribe with ConsumeTopics, does it possible to add ability to return error if topic unknown or client does not have rights to fetch from it or produce?
The text was updated successfully, but these errors were encountered: