topic_pattern() kafka rest proxy not working

[Ram Sharan Mittal]

when create a topic_pattern with http://docs.confluent.io/3.2.0/kafka-rest/docs/api.html#post--consumers-(string-group_name)-instances-(string-instance)-subscription and then get by http://docs.confluent.io/3.2.0/kafka-rest/docs/api.html#get--consumers-(string-group_name)-instances-(string-instance)-subscription is not returning topic pattern or topic list , even topic exist. any help

[Ram Sharan Mittal]

one more point 

but if topic_pattern are subscribe than try to subscribe topics it give error { "error_code": 40903, "message": "Illegal state: Subscription to topics, partitions and pattern are mutually exclusive" }

that means it know that topic pattern are subscribe. Now if you delete topic_pattern subscription and subscribe topics it do.

Whole point i am try to make it that why it is not returning topic_pattern by a get call

[Ram Sharan Mittal]

On Thursday, 27 April 2017 14:26:53 UTC+5:30, Ram Sharan Mittal wrote:

when create a topic_pattern with http://docs.confluent.io/3.2.0/kafka-rest/docs/api.html#post--consumers-(string-group_name)-instances-(string-instance)-subscription and then get by http://docs.confluent.io/3.2.0/kafka-rest/docs/api.html#get--consumers-(string-group_name)-instances-(string-instance)-subscription is not returning topic pattern or topic list , even topic exist. any help

Was using wrong pattern topic* instead of topic.*. but in return you don't get pattern you get topic which give topics name only

[Ewen Cheslack-Postava]

That's an interesting issue. I'm not sure there's any good way to catch it though -- at first I was thinking that if we have a regex subscription and after rebalance there are 0 partitions assigned then we could issue some kind of special error message. But that could be expected depending on how many consumers you have, i.e. you could get 0 partitions even if matching topics do exist.

-Ewen

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/d439bb0b-fbcd-40d5-bf9f-39e318e25d42%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Ram Sharan Mittal]

issue is fixed but not sure. When you get data from <rest-proxy>/consumers/cg8/instances/cg8-con-0/records?timeout=150, after that you get subscription , you will get topic list not pattern in response

On Tuesday, 2 May 2017 10:15:08 UTC+5:30, Ewen Cheslack-Postava wrote:

That's an interesting issue. I'm not sure there's any good way to catch it though -- at first I was thinking that if we have a regex subscription and after rebalance there are 0 partitions assigned then we could issue some kind of special error message. But that could be expected depending on how many consumers you have, i.e. you could get 0 partitions even if matching topics do exist.

-Ewen

On Thu, Apr 27, 2017 at 11:20 PM, Ram Sharan Mittal <mittalram...@gmail.com> wrote:

On Thursday, 27 April 2017 14:26:53 UTC+5:30, Ram Sharan Mittal wrote:

when create a topic_pattern with http://docs.confluent.io/3.2.0/kafka-rest/docs/api.html#post--consumers-(string-group_name)-instances-(string-instance)-subscription and then get by http://docs.confluent.io/3.2.0/kafka-rest/docs/api.html#get--consumers-(string-group_name)-instances-(string-instance)-subscription is not returning topic pattern or topic list , even topic exist. any help

Was using wrong pattern topic* instead of topic.*. but in return you don't get pattern you get topic which give topics name only

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.

To post to this group, send email to confluent...@googlegroups.com.