Github user r7raul1984 commented on the issue:
https://github.com/apache/eagle/pull/812
@jhsenjaliya In my opition , I don't think it is good time to upgrade
storm to 1.1.0. In my experience ,many companies do not use the latest version
.If you insist to upgrade storm, I recommend
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/812
i will update this PR with storm 1.1.0 and rebase it after 0.5 release.
---
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
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/812
Just worry about potential compatibility issue as `kafka` which was
refactored a lot recently and here are some tricky dependencies behavior in
`storm-kafka`
---
If your project is set up for it, you
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/812
i havent explicitly tested it, but from their
[docs](http://storm.apache.org/releases/1.0.2/storm-kafka.html), it looks
compatible with kafka 0.8.1.1 which is used in the example given on that
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/812
Have you tested about consuming `kafka:0.8.1` with `storm-kafka:1.0.2` ?
---
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
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/812
@jhsenjaliya building failed, could you please check again?
---
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
