[
https://issues.apache.org/jira/browse/KAFKA-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680461#comment-14680461
]
ASF GitHub Bot commented on KAFKA-1893:
---------------------------------------
GitHub user SinghAsDev opened a pull request:
https://github.com/apache/kafka/pull/128
KAFKA-1893: Allow regex subscriptions in the new consumer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SinghAsDev/kafka KAFKA-1893
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/128.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #128
----
commit 7294571b853979f85685ae6a49a4711202a64c04
Author: asingh <asi...@cloudera.com>
Date: 2015-07-28T00:05:48Z
KAFKA-1893: Allow regex subscriptions in the new consumer
----
> Allow regex subscriptions in the new consumer
> ---------------------------------------------
>
> Key: KAFKA-1893
> URL: https://issues.apache.org/jira/browse/KAFKA-1893
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Reporter: Jay Kreps
> Assignee: Ashish K Singh
> Priority: Critical
> Fix For: 0.8.3
>
>
> The consumer needs to handle subscribing to regular expressions. Presumably
> this would be done as a new api,
> {code}
> void subscribe(java.util.regex.Pattern pattern);
> {code}
> Some questions/thoughts to work out:
> - It should not be possible to mix pattern subscription with partition
> subscription.
> - Is it allowable to mix this with normal topic subscriptions? Logically
> this is okay but a bit complex to implement.
> - We need to ensure we regularly update the metadata and recheck our regexes
> against the metadata to update subscriptions for new topics that are created
> or old topics that are deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
