[GitHub] incubator-metron issue #310: METRON-495: Upgrade Storm to 1.0.x
Github user justinleet commented on the issue: https://github.com/apache/incubator-metron/pull/310 Closing this PR, as it's been superseded by Mike and Casey's follow on work at https://github.com/apache/incubator-metron/pull/318 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-metron issue #310: METRON-495: Upgrade Storm to 1.0.x
Github user ottobackwards commented on the issue: https://github.com/apache/incubator-metron/pull/310 I spent some time on this yesterday. I do not have a lot of Kafka/ZK/Storm experience - but I was hoping for something to stand out Unfortunately that was not the case. Can you share how you setup intellij for scala? I'm seeing intellij not finding the wrapper classes. Also - if you have any more information on the failing tests or guesses as to their cause that would help. Do we know if we should have a newer version of curator to go with the newer kafka/storm? --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-metron issue #310: METRON-495: Upgrade Storm to 1.0.x
Github user ottobackwards commented on the issue: https://github.com/apache/incubator-metron/pull/310 Justin - I have added your repo as a remote, checked out and branched storm-1.0 - when I do mvn test - it runs is actually working. Is there a different way to see the failing tests or more likely am I doing something wrong? --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [GitHub] incubator-metron issue #310: METRON-495: Upgrade Storm to 1.0.x
I would think pulling the band-aid off and getting to HDP 2.5 and HDF 2.0 would be worth it. Then jiras around taking advantage of the improvements in Storm can start. On October 14, 2016 at 18:11:32, justinleet (g...@git.apache.org) wrote: Github user justinleet commented on the issue: https://github.com/apache/incubator-metron/pull/310 As an aside, the reason for attempting to bump the version of Kafka is that there seems to be a bit of a catch where moving Storm to 1.0.1 causes problems with Kafka, but leaving it obviously means the packaging no longer lines up. If someone knows a way around that (or even better, a more correct way to handle that) without upgrading Kafka, I'd probably prefer to use that, and leave Kafka for another day. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-metron issue #310: METRON-495: Upgrade Storm to 1.0.x
Github user justinleet commented on the issue: https://github.com/apache/incubator-metron/pull/310 As an aside, the reason for attempting to bump the version of Kafka is that there seems to be a bit of a catch where moving Storm to 1.0.1 causes problems with Kafka, but leaving it obviously means the packaging no longer lines up. If someone knows a way around that (or even better, a more correct way to handle that) without upgrading Kafka, I'd probably prefer to use that, and leave Kafka for another day. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
