Add custom retry policy support to Topic reads & writes

[pnv1]

[Myllyenko]

@pnv1, can we somehow help prioritize this issue? Ability to classify topic API errors (detect storage exhaustion behind a topic in particular) is very important for us.

[pnv1]

@pnv1, can we somehow help prioritize this issue? Ability to classify topic API errors (detect storage exhaustion behind a topic in particular) is very important for us.

We have received similar request recently. I'll try to prioritize this issue, but I doubt it will be done in less then a month at least

[rusanovdmitry]

when calling the alter topic

topicClient
            .alterTopic(topicPath,
                AlterTopicSettings.newBuilder()
                    .addAddConsumer(Consumer.newBuilder()
                        .setName(consumerName)
                        .setImportant(false)
                        .setSupportedCodecs(SupportedCodecs.newBuilder()
                            .addCodec(Codec.RAW)
                            .build())
                        .build())
                    .build())
            .join()

Caused by: java.util.concurrent.CompletionException: yandex.cloud.iam.topicreader.ydb.topic.YdbTopicConsumerException: Could not add consumer access-service-as-klg1 to topic /global/iam/api_keys/updates, status = Status{code = OVERLOADED(code=400060), issues = [Check failed: path: '/global/iam/api_keys/updates/streamImpl', error: path is under operation (id: [OwnerId: 72075186248325098, LocalPathId: 246669], type: EPathTypePersQueueGroup, state: EPathStateAlter) (S_ERROR)]}
        at java.base/java.util.concurrent.CompletableFuture.wrapInCompletionException(CompletableFuture.java:323) ~[?:?]