GitHub user shanyu opened a pull request:
https://github.com/apache/storm/pull/552
Storm-818: storm-eventhubs configuration improvement and refactoring
In Storm-583 EventHubSpout and EventHubBolt implementation were added.
During the review and licensing clearance process, we've improved the code base
around the spout/bolt configuration. Specifically, the following changes need
to be checked in:
1. EventHubBolt improvement: add event formatter to format tuples into
bytes for EventHubs and support each bolt sending to a separate EH partition
etc.
2. Refactor EventHubSpoutConfig, use setXXX() instead of specifying
configuration in constructor for optional configurations.
3. EventHubSpoutConfig specify consumer group name
4. Workaround for Qpid bug that cannot receive messages from EventHubs in
rare cases
5. Upgrade to newer Qpid version 0.32
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shanyu/storm ehimprove
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/552.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 #552
----
commit e515492864092c16c2ecc86577a3be73ec79fa56
Author: Shanyu Zhao <[email protected]>
Date: 2015-05-13T19:26:53Z
storm-eventhubs improvement
EventHubBolt add event formatter to format tuples into bytes
Refactor EventHubSpoutConfig
Add support for specifying consumer group name
Workaround for Qpid issue that in rare cases messages cannot be received
Signed-off-by: Shanyu Zhao <[email protected]>
commit 1f13f15d0c0de233fd4cc4ff6d6de586c4736142
Author: Shanyu Zhao <[email protected]>
Date: 2015-05-13T21:50:02Z
Fix line endings so that the diff is meaningful.
Signed-off-by: Shanyu Zhao <[email protected]>
----
---
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.
---
