[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-10-17 Thread harshach
Github user harshach commented on the issue: https://github.com/apache/storm/pull/1702 @raviperi do you have JIRA filed here for this https://issues.apache.org/jira/browse/STORM/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-10-13 Thread srdo
Github user srdo commented on the issue: https://github.com/apache/storm/pull/1702 No, this seems fine. +1 --- 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,

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-10-13 Thread harshach
Github user harshach commented on the issue: https://github.com/apache/storm/pull/1702 +1. @srdo do you have any further comments pending. --- 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

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-10-11 Thread revans2
Github user revans2 commented on the issue: https://github.com/apache/storm/pull/1702 I am not really familiar with EventHub all that much so I don't really feel all that confident in reviewing it. I mostly jumped on to answer a few generic questions. --- If your project is set up

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-10-11 Thread raviperi
Github user raviperi commented on the issue: https://github.com/apache/storm/pull/1702 @revans2 Please let me know if you have further comments. --- 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

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-09-27 Thread raviperi
Github user raviperi commented on the issue: https://github.com/apache/storm/pull/1702 Created a new PR https://github.com/apache/storm/pull/1717 for the master branch. Created a new JIRA that reflects the need for the aboce work. STORM-2127 - Storm-eventhubs should use

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-09-27 Thread raviperi
Github user raviperi commented on the issue: https://github.com/apache/storm/pull/1702 The latest PR addresses the above comments . Move dependencies to parent pom . Revert changes to versions to reflect naming convention. I will be sending a different PR to master

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-09-27 Thread revans2
Github user revans2 commented on the issue: https://github.com/apache/storm/pull/1702 Is there a similar pull request to master? --- 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

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-09-22 Thread HeartSaVioR
Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1702 Btw, IMO, upgrading the dependency is worth to file an issue. @raviperi Could you file it and copy description of PR to issue's description? --- If your project is set up for it, you can

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-09-22 Thread srdo
Github user srdo commented on the issue: https://github.com/apache/storm/pull/1702 Hm, nevermind the new client, it requires Java 8. It's still an option for Storm 2.0 though. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

2016-09-22 Thread srdo
Github user srdo commented on the issue: https://github.com/apache/storm/pull/1702 This seems fine once the storm versions are reverted, though you should get this on the master branch first. I'd like to mention before you spend too much time on trying to make the spout run reliably,