Hello Julien,
Sorry for asking so late, but one detail puzzles my in this
discussion: according to semantic versioning, the change of major
version number is meant to introduce changes breaking compatibility.
Unless I have missed something, I do not see any changes that would
break compatibility
rzo1 merged PR #3608:
URL: https://github.com/apache/storm/pull/3608
--
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
I agree on the need to fix logviewer functionality so that it works in a
Kubernetes deployment (eg AWS EKS or GKE).
Sent from Yahoo Mail for iPhone
On Thursday, December 7, 2023, 4:26 AM, Richard Zowalla
wrote:
It might be possible to build an abstraction layer + java 21-based
module, so
It might be possible to build an abstraction layer + java 21-based
module, so ppl can decide (for ex by configuration) to switch to it or
not. If you do not activley decide to use it, it won't be a difference
to how it is currently working. Might need some carefully thinking and
some eyes on other
Agreed for leaving fiber projet aside from 3.x
Re-logviewer : how about my idea to use storm-ui's app server and
write some kind of proxy servlet to make all traffic related to logs
retrieval going to storm UI ?
Le jeu. 7 déc. 2023 à 13:06, Julien Nioche
a écrit :
>
> Thanks Alexandre,
>
> I
Thanks Alexandre,
I haven't looked nor know anything about fibers but it sounds promising.
Forcing Java 21 would be problematic I think.
Given that it is a fundamental change, maybe this could live in a separate
branch until thoroughly tested and Java 21 is the norm. What do you think?
Hello Julien,
Excellent initiative indeed !
I am very fond of "Find a way of having the Logviewer work in Docker"
topic, because I think it's similar to a shorter time need which I
have when deploying AWS EC2 with a VPN to avoid exposure of "internal
VMs" : in this case, the public FQDN of
Hi,
Now that Storm is active again and we are getting regular releases, should
we try to come up with a roadmap for the Storm 3.x?
Here are a few things that come to mind
- Finish the migration from Clojure to Java (it is still used in the
tests I think)
- Find a way of having the
rzo1 merged PR #3610:
URL: https://github.com/apache/storm/pull/3610
--
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
