You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by S G <sg...@gmail.com> on 2016/08/25 19:58:50 UTC
Package name changes for 3rd party storm dependencies
Hi,
Our project is planning to upgrade storm from 0.10.0 to 1.0.2
We use a couple of 3rd party storm dependencies like storm-jms,
https://github.com/HolmesNL/kafka-spout etc.
Some of these projects have plans to upgrade soon to 1.0.2 but some do not
have it on their roadmap.
What is the best strategy to proceed in such a case?
I do not want to copy-and-maintain all the 3rd parties code myself.
Is there a maven-trick published somewhere to do this?
Thanks
SG
Re: Package name changes for 3rd party storm dependencies
Posted by Abhishek Agarwal <ab...@gmail.com>.
Hi,
Did you explore using the KafkaSpout available in the apache storm
repository? You can find a stronger community support for the code. We have
two flavours of Kafka spout and old flavour works pretty well with 0.8.2.2
version of kafka.
On Mon, Aug 29, 2016 at 9:56 AM, S G <sg...@gmail.com> wrote:
> Hi Jungtaek,
>
> My project used storm-jms which was recently upgraded. (I think it might be
> good to consider moving that code-base to storm/external)
> Another one some of us are using is HolmesNL/kafka-spout (My PR:
> https://github.com/HolmesNL/kafka-spout/pull/20) but it seems that the
> author there wants someone to test before upgrading.
>
> Thanks
> SG
>
>
> On Sun, Aug 28, 2016 at 8:18 PM, Jungtaek Lim <ka...@gmail.com> wrote:
>
> > Hi,
> >
> > Could you enumerate which projects don't catch up the change of Apache
> > Storm 1.0.0+?
> > I think we need to get in touch and let them follow up (or we could help)
> > recent change.
> >
> > Thanks,
> > Jungtaek Lim (HeartSaVioR)
> >
> > 2016년 8월 26일 (금) 오후 5:36, Abhishek Agarwal <ab...@gmail.com>님이 작성:
> >
> > > In your pom, you can add class relocation (
> > >
> > > https://maven.apache.org/plugins/maven-shade-plugin/
> > examples/class-relocation.html
> > > )
> > >
> > > You can add the patterns in this class -
> > >
> > > https://github.com/apache/storm/blob/master/storm-
> > rename-hack/src/main/java/org/apache/storm/hack/StormShadeRequest.java
> > >
> > >
> > >
> > >
> > > On Fri, Aug 26, 2016 at 1:28 AM, S G <sg...@gmail.com>
> wrote:
> > >
> > > > Hi,
> > > >
> > > > Our project is planning to upgrade storm from 0.10.0 to 1.0.2
> > > > We use a couple of 3rd party storm dependencies like storm-jms,
> > > > https://github.com/HolmesNL/kafka-spout etc.
> > > >
> > > > Some of these projects have plans to upgrade soon to 1.0.2 but some
> do
> > > not
> > > > have it on their roadmap.
> > > >
> > > > What is the best strategy to proceed in such a case?
> > > >
> > > > I do not want to copy-and-maintain all the 3rd parties code myself.
> > > >
> > > > Is there a maven-trick published somewhere to do this?
> > > >
> > > > Thanks
> > > > SG
> > > >
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Abhishek Agarwal
> > >
> >
>
--
Regards,
Abhishek Agarwal
Re: Package name changes for 3rd party storm dependencies
Posted by S G <sg...@gmail.com>.
Hi Jungtaek,
My project used storm-jms which was recently upgraded. (I think it might be
good to consider moving that code-base to storm/external)
Another one some of us are using is HolmesNL/kafka-spout (My PR:
https://github.com/HolmesNL/kafka-spout/pull/20) but it seems that the
author there wants someone to test before upgrading.
Thanks
SG
On Sun, Aug 28, 2016 at 8:18 PM, Jungtaek Lim <ka...@gmail.com> wrote:
> Hi,
>
> Could you enumerate which projects don't catch up the change of Apache
> Storm 1.0.0+?
> I think we need to get in touch and let them follow up (or we could help)
> recent change.
>
> Thanks,
> Jungtaek Lim (HeartSaVioR)
>
> 2016년 8월 26일 (금) 오후 5:36, Abhishek Agarwal <ab...@gmail.com>님이 작성:
>
> > In your pom, you can add class relocation (
> >
> > https://maven.apache.org/plugins/maven-shade-plugin/
> examples/class-relocation.html
> > )
> >
> > You can add the patterns in this class -
> >
> > https://github.com/apache/storm/blob/master/storm-
> rename-hack/src/main/java/org/apache/storm/hack/StormShadeRequest.java
> >
> >
> >
> >
> > On Fri, Aug 26, 2016 at 1:28 AM, S G <sg...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Our project is planning to upgrade storm from 0.10.0 to 1.0.2
> > > We use a couple of 3rd party storm dependencies like storm-jms,
> > > https://github.com/HolmesNL/kafka-spout etc.
> > >
> > > Some of these projects have plans to upgrade soon to 1.0.2 but some do
> > not
> > > have it on their roadmap.
> > >
> > > What is the best strategy to proceed in such a case?
> > >
> > > I do not want to copy-and-maintain all the 3rd parties code myself.
> > >
> > > Is there a maven-trick published somewhere to do this?
> > >
> > > Thanks
> > > SG
> > >
> >
> >
> >
> > --
> > Regards,
> > Abhishek Agarwal
> >
>
Re: Package name changes for 3rd party storm dependencies
Posted by Jungtaek Lim <ka...@gmail.com>.
Hi,
Could you enumerate which projects don't catch up the change of Apache
Storm 1.0.0+?
I think we need to get in touch and let them follow up (or we could help)
recent change.
Thanks,
Jungtaek Lim (HeartSaVioR)
2016년 8월 26일 (금) 오후 5:36, Abhishek Agarwal <ab...@gmail.com>님이 작성:
> In your pom, you can add class relocation (
>
> https://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html
> )
>
> You can add the patterns in this class -
>
> https://github.com/apache/storm/blob/master/storm-rename-hack/src/main/java/org/apache/storm/hack/StormShadeRequest.java
>
>
>
>
> On Fri, Aug 26, 2016 at 1:28 AM, S G <sg...@gmail.com> wrote:
>
> > Hi,
> >
> > Our project is planning to upgrade storm from 0.10.0 to 1.0.2
> > We use a couple of 3rd party storm dependencies like storm-jms,
> > https://github.com/HolmesNL/kafka-spout etc.
> >
> > Some of these projects have plans to upgrade soon to 1.0.2 but some do
> not
> > have it on their roadmap.
> >
> > What is the best strategy to proceed in such a case?
> >
> > I do not want to copy-and-maintain all the 3rd parties code myself.
> >
> > Is there a maven-trick published somewhere to do this?
> >
> > Thanks
> > SG
> >
>
>
>
> --
> Regards,
> Abhishek Agarwal
>
Re: Package name changes for 3rd party storm dependencies
Posted by Abhishek Agarwal <ab...@gmail.com>.
In your pom, you can add class relocation (
https://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html
)
You can add the patterns in this class -
https://github.com/apache/storm/blob/master/storm-rename-hack/src/main/java/org/apache/storm/hack/StormShadeRequest.java
On Fri, Aug 26, 2016 at 1:28 AM, S G <sg...@gmail.com> wrote:
> Hi,
>
> Our project is planning to upgrade storm from 0.10.0 to 1.0.2
> We use a couple of 3rd party storm dependencies like storm-jms,
> https://github.com/HolmesNL/kafka-spout etc.
>
> Some of these projects have plans to upgrade soon to 1.0.2 but some do not
> have it on their roadmap.
>
> What is the best strategy to proceed in such a case?
>
> I do not want to copy-and-maintain all the 3rd parties code myself.
>
> Is there a maven-trick published somewhere to do this?
>
> Thanks
> SG
>
--
Regards,
Abhishek Agarwal