ASF GitHub Bot commented on METRON-495:

Github user justinleet commented on the issue:

    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.

> Upgrade Storm to 1.0.x
> ----------------------
>                 Key: METRON-495
>                 URL: https://issues.apache.org/jira/browse/METRON-495
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Justin Leet
>            Assignee: Justin Leet
> As listed at https://storm.apache.org/2016/04/12/storm100-released.html, 
> there's a variety of improvements with Storm 1.0.  The obvious and likely 
> most important improvement is to performance, but a variety of other 
> improvements are noted on that link.
> There are several changes that have to occur in order to make this upgrade.  
> As noted in http://storm.apache.org/releases/current/index.html, Storm's code 
> packages moved from backtype.storm to org.apache.storm, meaning all 
> topologies have to be recompiled if that change.  There is a runtime 
> converter to run things in place with backtype.storm, but this doesn't appear 
> to be enough for our case because a couple interfaces change from byte[] to 
> ByteBuffer (somewhat, but not entirely, related to 
> https://issues.apache.org/jira/browse/STORM-1449). Even without this issue, 
> the long term solution is to use the new package naming.
> In addition, our dev instances right now spin up an HDP 2.4 instance, which 
> matches our current version of Storm. HDP 2.5 uses Storm 1.0.1, so to migrate 
> to Storm 1.0.x, I'd prefer to match that version, rather than going to 1.0.2.

This message was sent by Atlassian JIRA

Reply via email to