-
Notifications
You must be signed in to change notification settings - Fork 552
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
Returned config_type in DescribeConfigs is always 0 #4170
Comments
Thanks @weeco I'm surprised this field isn't filled it. But this should be an easy fix. |
Took a look at this to see what might be involved to fix it. This is what I found. In franz-go v1.4.0 it shows that the version of the Kafka API is expected to be at least 3 in order to have config property types included in the response. However, Redpanda only seems to support up to version 2 for the DescribeConfigs API:
I tested with kcl against a Redpanda cluster and sure enough, it negotiates with DescribeConfigs v2. So even though I've specified the
Assuming my understanding of this is correct, it looks like Redpanda would need to support version 3 which includes the property types in the response. I think this is the KIP: |
Apologies, I realise now that I confused the property type and resource type the property is associated with. I've hidden my comment because it's unrelated to the issue at hand. |
@peter-evans You were actually completely right, I used the wrong property name in my initial issue description. I have updated the issue description accordingly, thanks for looking at this too! |
Ah, good to know! 😆 |
@graphcareful Is this customer-facing/does it require a doc update? |
@NyaliaLui should comment on this as he is DRIing this feature. |
@Feediver1
EDIT: I had a brief slack convo with @graphcareful. This change is not customer facing and it does not require a doc update. |
Version & Environment
Redpanda version: (use
rpk version
): v22.1.4Kafka client: franz-go v1.6.0
What went wrong?
When describing configs (either broker or topic) the returned
config_type
is always zero (unknown
). The reported API version forDescribeConfigs
in the API versions response is v2. This property has been introduced in v3 of this request.Version 2:
Version 3:
A couple metadata properties have been added as per KIP-569
What should have happened instead?
How to reproduce the issue?
config_type
(either topics or brokers is where I have observed this)Additional information
Usecase is Kowl:
The text was updated successfully, but these errors were encountered: