Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/651#issuecomment-13151
@tandrup can you please open a JIRA here
https://issues.apache.org/jira/browse/STORM/ and also update the PR with JIRA
number in the title.
---
If your project is set
Github user lazyval commented on a diff in the pull request:
https://github.com/apache/storm/pull/651#discussion_r35654576
--- Diff:
external/storm-eventhubs/src/main/java/org/apache/storm/eventhubs/spout/EventDataScheme.java
---
@@ -42,6 +44,9 @@
AmqpValue amqpValue
Github user rsltrifork commented on the pull request:
https://github.com/apache/storm/pull/651#issuecomment-124075611
Event hub (and Kafka) play well into event source architectures as event
ingest point for later Storm processing to downstream stateful consumers.
Advanced eve
GitHub user tandrup opened a pull request:
https://github.com/apache/storm/pull/651
Eventhub spout meta data
Add "partition","seq-number" fields to emitted tupples for event sourcing
consumers, which need to preserve partition order and be able to replay.
You can merge this pull r
