[
https://issues.apache.org/jira/browse/KAFKA-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514829#comment-16514829
]
Ismael Juma commented on KAFKA-7064:
------------------------------------
Looks like there is an issue with the link above, so here's another one from a
manually triggered run:
http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/2018-06-15--001.1529092440--apache--trunk--dad19ac/ClientCompatibilityFeaturesTest/run_compatibility_test/broker_version%3D0.11.0.2/0/client_compatibility_test_output.txt
> "Unexpected resource type GROUP" when describing broker configs using latest
> admin client
> -----------------------------------------------------------------------------------------
>
> Key: KAFKA-7064
> URL: https://issues.apache.org/jira/browse/KAFKA-7064
> Project: Kafka
> Issue Type: Bug
> Reporter: Rohan Desai
> Assignee: Andy Coates
> Priority: Blocker
> Fix For: 2.0.0
>
>
> I'm getting the following error when I try to describe broker configs using
> the admin client:
> {code:java}
> org.apache.kafka.common.errors.InvalidRequestException: Unexpected resource
> type GROUP for resource 0{code}
> I think its due to this commit:
> [https://github.com/apache/kafka/commit/49db5a63c043b50c10c2dfd0648f8d74ee917b6a]
>
> My guess at what's going on is that now that the client is using
> ConfigResource instead of Resource it's sending a describe request for
> resource type BROKER w/ id 3, while the broker associates id 3 w/ GROUP
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
