GitHub user sumitchawla opened a pull request:
https://github.com/apache/storm/pull/561
STORM-817: Support for Kafka Wildcard topics
Support for Wildcard match of topics based on Config -
"kafka.topic.wildcard.match". If this config is specified then Topics matching
the pattern are picked for listening to messages.
Implementation Details:
1. DynamicBrokerReader now returns a list of GlobalPartitionInformation.
Each object is tied to a topic.
2. Partition object now has a topic. Each parition belongs to a
specific topic
3. DynamicPartitonConnections keeps a map of topic_partiton registration
4. Kafka Metrics are written per topic.
5. PartitionManager uses Partition.topic for calculating commit path.
Commit path for wildcard topic scenario will be
_spoutConfig.id/topic_ABC/partition_0; For non-wildcard use, the path will be
_spoutConfig.id/partition_0. This way the change is backward compatible with
previously committed ZK offsets.
6. New Test case DynamicBrokerReaderTests. testGetBrokerInfoWildcardMatch
for testing topic discovery.
7. Manually tested Kafka Single Topic, Wildcard topics, Trident Topic,
Wildcard topics.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sumitchawla/storm master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/561.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 #561
----
commit 455435adffd873d98eedc77f428b7d76f94f8bba
Author: Sumit Chawla <[email protected]>
Date: 2015-05-22T21:38:30Z
STORM-817: Support for Kafka Wildcard topics
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
