You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/09/26 04:20:04 UTC
[jira] [Updated] (STORM-818) storm-eventhubs configuration
improvement and refactoring
[ https://issues.apache.org/jira/browse/STORM-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Kellogg updated STORM-818:
-------------------------------
Component/s: Storm-eventhubs
> storm-eventhubs configuration improvement and refactoring
> ---------------------------------------------------------
>
> Key: STORM-818
> URL: https://issues.apache.org/jira/browse/STORM-818
> Project: Apache Storm
> Issue Type: Bug
> Components: Storm-eventhubs
> Affects Versions: 0.9.3
> Reporter: shanyu zhao
> Assignee: shanyu zhao
> Fix For: 0.10.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)