STORM-4021: Add worker hooks via storm.yaml configuration file

[Harish Madineni]

Why can't I add worker hooks via the storm.yaml configuration file?
Is it going to affect performance?
Any difference between adding a worker hook for a topology vs in configuration 
file? If any?

Re: Storm 2.6.1 ?

[Julien Nioche]

+1 to a 2.6.1 release

The nightlies are at https://nightlies.apache.org/storm/
A couple of changes were merged today, I'll try a nightly next week

J

On Fri, 26 Jan 2024 at 07:40, Richard Zowalla  wrote:

> Hi all,
>
> we had some fixes and dependency updates in Storm since our last
> release.
>
> Any objections in going for a 2.6.1 soon? Any lib upgrades we need to
> include prior?
>
> Did someone test our nightlies already?
>
>
> Gruß
> Richard
>


-- 
*Julien Nioche *


digitalpebble.com 

Re: [PR] STORM-4028 - Curator 5.6.0 (storm)

[via GitHub]

rzo1 merged PR #3624:
URL: https://github.com/apache/storm/pull/3624


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] STORM-4027 - Kryo 5.6.0 (storm)

[via GitHub]

rzo1 merged PR #3623:
URL: https://github.com/apache/storm/pull/3623


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] STORM-4026 - Thrift 0.19.0 (storm)

[via GitHub]

rzo1 merged PR #3622:
URL: https://github.com/apache/storm/pull/3622


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Storm 2.6.1 ?

[Alexandre Vermeerbergen]

I have no objection for such Storm 2.7.0 to Storm 2.6.1 renaming !
(so then nightly build shall automatically lead to 2.6.1 one renaming is done ?)

Le ven. 26 janv. 2024 à 09:50, Richard Zowalla  a écrit :
>
> Hi Alexandre,
>
> I think, that we can rename the milestone/version from 2.7.0 to 2.6.1
> as we do not have any public facing breaking changes in the API
> (afaik). So instead of going 2.7.0, we can just do a 2.6.1 (imho).
>
> Gruß
> Richard
>
> Am Freitag, dem 26.01.2024 um 09:48 +0100 schrieb Alexandre
> Vermeerbergen:
> > Hello Richard,
> >
> > +1, you must read my mind :)
> >
> > I am especially interest to get
> > https://issues.apache.org/jira/browse/STORM-4025 backported to 2.6.1
> > ;
> > and your recent dependency update won Kryo, please.
> >
> > Kind regards,
> > ALexandre
> >
> > Le ven. 26 janv. 2024 à 08:40, Richard Zowalla  a
> > écrit :
> > >
> > > Hi all,
> > >
> > > we had some fixes and dependency updates in Storm since our last
> > > release.
> > >
> > > Any objections in going for a 2.6.1 soon? Any lib upgrades we need
> > > to
> > > include prior?
> > >
> > > Did someone test our nightlies already?
> > >
> > >
> > > Gruß
> > > Richard
>

Re: Storm 2.6.1 ?

[Richard Zowalla]

Hi Alexandre,

I think, that we can rename the milestone/version from 2.7.0 to 2.6.1
as we do not have any public facing breaking changes in the API
(afaik). So instead of going 2.7.0, we can just do a 2.6.1 (imho).

Gruß
Richard

Am Freitag, dem 26.01.2024 um 09:48 +0100 schrieb Alexandre
Vermeerbergen:
> Hello Richard,
> 
> +1, you must read my mind :)
> 
> I am especially interest to get
> https://issues.apache.org/jira/browse/STORM-4025 backported to 2.6.1
> ;
> and your recent dependency update won Kryo, please.
> 
> Kind regards,
> ALexandre
> 
> Le ven. 26 janv. 2024 à 08:40, Richard Zowalla  a
> écrit :
> > 
> > Hi all,
> > 
> > we had some fixes and dependency updates in Storm since our last
> > release.
> > 
> > Any objections in going for a 2.6.1 soon? Any lib upgrades we need
> > to
> > include prior?
> > 
> > Did someone test our nightlies already?
> > 
> > 
> > Gruß
> > Richard

Re: Storm 2.6.1 ?

[Alexandre Vermeerbergen]

Hello Richard,

+1, you must read my mind :)

I am especially interest to get
https://issues.apache.org/jira/browse/STORM-4025 backported to 2.6.1 ;
and your recent dependency update won Kryo, please.

Kind regards,
ALexandre

Le ven. 26 janv. 2024 à 08:40, Richard Zowalla  a écrit :
>
> Hi all,
>
> we had some fixes and dependency updates in Storm since our last
> release.
>
> Any objections in going for a 2.6.1 soon? Any lib upgrades we need to
> include prior?
>
> Did someone test our nightlies already?
>
>
> Gruß
> Richard

[PR] STORM-4028 - Curator 5.6.0 (storm)

[via GitHub]

rzo1 opened a new pull request, #3624:
URL: https://github.com/apache/storm/pull/3624

   ## What is the purpose of the change
   
   [*(Explain why we should have this 
change)*](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425=12353185)
   
   ## How was the change tested
   
   - CI


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[PR] STORM-4027 - Kryo 5.6.0 (storm)

[via GitHub]

rzo1 opened a new pull request, #3623:
URL: https://github.com/apache/storm/pull/3623

   ## What is the purpose of the change
   
   - https://github.com/EsotericSoftware/kryo/releases
   
   ## How was the change tested
   
   - CI


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org