Glad to see yet this upcoming Apache Storm 2.6.3 release !
However, I'm afraid I won't be able to evaluate the release candidate
before I'm back from my vacations - 30th of July ; but don't mind if
vote passes without me.
(I'm especially interested to try
Hello,
Yes Redis server licensing became non-OSS friendly, but I don't
understand what would be Storm's dependency on Redis server : don't we
we just need a Redis client, such as Jedis (this later has a MIT
License) ?
Alex
Le lun. 13 mai 2024 à 11:51, Richard Zowalla a écrit :
>
> Hi all,
>
>
Thanks a lot Richard for this very smooth & efficient release !
Alexandre
Le ven. 5 avr. 2024 à 19:37, Richard Zowalla a écrit :
>
> Hi,
>
> this vote passes with the following votes:
>
> +1 Julien Nioche (binding)
> +1 Alexandre Vermeerbergen (binding)
> +1 Richar
+1 (binding)
tested on my pre-production Storm cluster with 15 topologies on 6
supervisor nodes (and 3 zookeeper nodes), since all topologies relying
on Apache Kafka topics (with kafka-monitoring showing lags per
partitions & per topic in Storm UI, this time it's not broken ;) and
some topologies
+1 and I commit that I will test 2.6.2RC with by large set of
topologies on my preproduction !
Alexandre
Le jeu. 28 mars 2024 à 15:45, Julien Nioche
a écrit :
>
> +1 from me
>
>
> On Thu, 28 Mar 2024 at 13:58, Richard Zowalla wrote:
>
> > Hi,
> >
> > any objections in doing a 2.6.2 after
+1 I agree that JIRA is overkill for the simple needs of incidents /
enhancements tracking of Apache Storm
Alexandre
Le jeu. 22 févr. 2024 à 12:18, Richard Zowalla a écrit :
>
> Hi all,
>
> The ASF JIRA instance no longer allows users to self-sign-up (though it
> DOES allow us to invite
[+1] binding
Tested this 2.6.1 RC1 using binary artifacts on my Storm preproduction
cluster (6 Supervisor VMs) after having rebuilt my 14 Storm topologies
with updated 2.6.1 RC1 dependencies (including storm-kafka-client and
storm-hdfs), on Redhat 8.7 Linux x64 and with IBM Semeru JDK 21.0.1
aven:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1110/org/apache/storm/storm-kafka-client/2.6.1/
>
> Hope it helps
> Richard
>
>
> Am Dienstag, dem 30.01.2024 um 16:02 +0100 schrieb Alexandre
> Vermeerbergen:
> > Other question: to test
> > http
ag, dem 30.01.2024 um 14:09 +0100 schrieb Alexandre
> Vermeerbergen:
> > Hi Richard,
> >
> > The link to "Storm Source and Binary Release with sha512 signature
> > files" is missing, can you please re-send the vote mail ?
> >
> > Thanks,
> > Alexan
Hi Richard,
The link to "Storm Source and Binary Release with sha512 signature
files" is missing, can you please re-send the vote mail ?
Thanks,
Alexandre
Le mar. 30 janv. 2024 à 09:42, Richard Zowalla a écrit :
>
> Hi ladies & lords,
>
> I have posted a first release candidate for Apache
I also updated my preproduction 10+ topologies with Storm snapshot
generated 20240128
=> everything runs fine and I confirm STORM-4025 is fixed !
Alex
Le lun. 29 janv. 2024 à 14:37, Julien Nioche
a écrit :
>
> Hi,
>
> Ran a StormCrawler toplogy with a nightly - looking good, no issues found
>
Hi Julien,
It's very nice that your submitted a Sorm-related topic for this
conference, I wish your proposal to be accepted !
Unfortunately I won't be able to travel at that time, I hope to see
you in broadcasts or records of your future session (betting it'll be
accepted :)
Alex
Le sam. 27
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
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,
>
Hello,
I would have voted [0] if possible, but only [+1] or [-1] are proposed ;)
Indeed, regarding Docker images, I tend to be reluctant to use
community images appart from OS base ones and built mine based on my
actual needs which are:
1. To use a specific JVM (I'm more found of OpenJ9 - aka
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 projects.
>
> Am Donnerstag, dem 07.12.2023 um 13:24 +0100 schrieb Alexandre
> Vermeerbergen:
> > Agreed for leaving
ink?
>
> Re-logviewer: it is something that has been bugging people for a while and
> that a lot of us would like to see fixed I think. Sadly, I don't have a
> clue on how to do it.
>
> Julien
>
> On Thu, 7 Dec 2023 at 11:01, Alexandre Vermeerbergen <
> avermeerber...@gmai
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
Hello guys,
I have a weird idea bugging my mind, so let me share it and if that's
improductive/dead end, then I'll forget it :)
I have been reading a few sources about the notion of Fibers in Java
(aka Loom Project) which are generally available with Java 21.
There's an optional "virtual
Hello,
+1 (binding)
tested with 13 topologies running on a 7 nodes cluster of Supervisors
on Redhat Linux 8.7 with IBM Semeru 17.0.8.1, with dependencies on:
storm-kafka-client
storm-kafka-monitoring
storm-hdfs
and... all dependencies on Java EE (mostly javax.json) migrated on our
side to
Hello,
Yesterday, I have upgraded my pre-production cluster "at scale" with
Storm 2.6.0 RC1, and *this time* this is with all my 10+ topologies
rebuilt using dependencies at same version (not based on previous
2.5.0 dependencies).
So far everything is running smoothly (CPU/IOPS/Memory loads are
ps://github.com/apache/storm/blob/master/external/storm-kafka-monitor/pom.xml
> >
> >
> > Am Mittwoch, dem 15.11.2023 um 15:02 +0100 schrieb Alexandre
> > Vermeerbergen:
> > > I had found yet another thing that must be fixed before starting
> >
jakarta.xml.bind-api
>
>
>
> to the related pom in the /external module [1]
>
> Gruß
> Richard
>
> [1]
> https://github.com/apache/storm/blob/master/external/storm-kafka-monitor/pom.xml
>
>
> Am Mittwoch, dem 15.11.2023 um 15:02 +0100 schrieb Alexand
archive out
of the box?
Thanks,
Alexandre
Le mar. 14 nov. 2023 à 17:50, Alexandre Vermeerbergen
a écrit :
>
> Good news on my side:
> * First test with 2.6.0 snapshot 2023/11/14 with a single Supervisor host is
> OK
>=> I will soon (tomorrow) be able to upgrade my pre p
Good news on my side:
* First test with 2.6.0 snapshot 2023/11/14 with a single Supervisor host is OK
=> I will soon (tomorrow) be able to upgrade my pre production
cluster to have a wider scope & performance results "at scale"
* My crazy attempt to convert all my topologies code from Java EE
Thanks Richard !
I am starting a release of my code based on this new Storm 2.6.0
snapshot 20231114, and I will upgrade our pre-production (running with
previous 2.6.0 snapshot of 2nd of November + few hand applies patches)
On a side note, I have made a crazy test yesterday, which was to
migrate
e but as a
> > task on which we could work after having a new version in the pipeline
> >
> > wdyt?
> >
> > Gruß
> > Richard
> >
> > Am Sonntag, dem 12.11.2023 um 09:40 +0100 schrieb Alexandre
> > Vermeerbergen:
> > > Thank Richard for the great
on
> > the list / thread, so we can create tickets for it
> >
> > There might be some false positives but will give good insights.
> >
> > Gruß
> > Richard
> >
> >
> > [1] https://github.com/anchore/grype
> > Am Donnerstag, dem 09.11.2023
At this moment that's the CVE which I found using Storm 2.6.0 snapshot 20231102.
And since there's a commons-text-1.11.0.jar available, I guess we
should directly jump to this version.
Le jeu. 9 nov. 2023 à 08:49, Alexandre Vermeerbergen
a écrit :
>
> Yet another finding on my side to &qu
mons-text-1.10.0.jar
The second one is okay from
https://www.cvedetails.com/cve/CVE-2022-42889/ perspective, but not
the first one.
I will continue checking if there are other CVEs...
Thanks,
Alexandre
Le mar. 7 nov. 2023 à 17:43, Alexandre Vermeerbergen
a écrit :
>
> Oh thank you very much
> > You pushed on your own branch. You would need to push to apache/storm
> > main branch or open a PR ;-)
> >
> > Am Samstag, dem 04.11.2023 um 10:36 +0100 schrieb Alexandre
> > Vermeerbergen:
> > > Just did a 'git push' with that trivial fix... is that enough?
&g
code with *mvn clean package -U *or delete the
> content of* ~/.m2/repository/org/apache/storm/ *beforehand?
>
> Julien
>
> On Sat, 4 Nov 2023 at 19:57, Alexandre Vermeerbergen <
> avermeerber...@gmail.com> wrote:
>
> > Yes another regression I found with my topologi
Le sam. 4 nov. 2023 à 20:57, Alexandre Vermeerbergen
a écrit :
>
> Yes another regression I found with my topologies (built with 2.5.0
> dependencies) running to Storm 2.6.0 SNAPSHOT 2023/11/02: I have seen
> several exceptions like this one:
>
> 2023-11-04 18:43:31.696 o.a.s
ng since many
upgrades, of course it's not an excuse...
I'll fix our code & continue checking if I see other impacts of 2.5.0
-> 2.6.0 upgrade...
Thanks,
Alexandre
Le sam. 4 nov. 2023 à 10:36, Alexandre Vermeerbergen
a écrit :
>
> Just did a 'git push' with that trivial fix... is that enoug
Just did a 'git push' with that trivial fix... is that enough?
Le sam. 4 nov. 2023 à 09:34, Richard Zowalla a écrit :
>
> You can do as you like ;-)
>
> Am 4. November 2023 08:54:48 MEZ schrieb Alexandre Vermeerbergen
> :
> >I mean :
> >
> >Can I keep using my
I mean :
Can I keep using my
'STORM-3958-Capacity-to-set-St
orm-UI's-title-in-conf/storm.yaml'
branch to push this fix, or should I create a new one?
Le sam. 4 nov. 2023 à 08:53, Alexandre Vermeerbergen
a écrit :
>
> Can you keep using my
> 'STORM-3958-Capacity-to-set-Storm-UI's-titl
n between, so not a big deal.
>
> Am 4. November 2023 08:01:54 MEZ schrieb Alexandre Vermeerbergen
> :
> >Temporary workaround for the Storm UI title's regression: run this
> >command on the title-template.html file (in
> >storm-stable/public/templates directory) after ha
this regression.
Alexandre
Le sam. 4 nov. 2023 à 07:52, Alexandre Vermeerbergen
a écrit :
>
> Updates regarding my test with Storm 2.6.0 Snapshot 2023/11/02:
> 1. I have modified my KO bolts using this pattern in their prepare() method:
>
>long cacheMaxSize =
> Long.parse
ickest way for this very simple fix to be delivered ?
Thanks,
Alexandre
Le ven. 3 nov. 2023 à 20:57, Alexandre Vermeerbergen
a écrit :
>
> Thanks Richard for the analysis.
>
> My thought on this are very simple: let me fix my own old code, after
> all this was impacting only one of my
wer JSON library works as expected
> (although it might break backward compatibility).
> Unchecked casts are always evil, imho. In your specific case, it might
> be more save to cast to "Number" and than invoke "longValue()" instead.
>
> Nevertheless, we might being
lies area.
> > >
> > > This new bundle works as expected in my deployment but happy to receive
> > > additional feedback before getting up a first release candidate ;-)
> > >
> > > Am Montag, dem 30.10.2023 um 08:21 +0100 schrieb Richard Zowall
e getting up a first release candidate ;-)
> >
> > Am Montag, dem 30.10.2023 um 08:21 +0100 schrieb Richard Zowalla:
> > > Hi Alexandre,
> > >
> > > we are not in a hurry here :) - take as much as time you need.
> > >
> > > Gruß
> > > Richard
dditional feedback before getting up a first release candidate ;-)
>
> Am Montag, dem 30.10.2023 um 08:21 +0100 schrieb Richard Zowalla:
> > Hi Alexandre,
> >
> > we are not in a hurry here :) - take as much as time you need.
> >
> > Gruß
> > Richard
> >
Hello Richard,
Okay, I'm more than happy to do that with my pre-production cluster
(~10 topologies) using the binary artifacts.
Would it be OK if I can use up to end of this week so that I'll be
able to have enough time to check all potential issues that this
upgrade bring?
Thanks,
Alexandre
Thank you very much for casting this vote Richard !
Le jeu. 19 oct. 2023 à 08:52, Richard Zowalla a écrit :
>
> Hi all,
>
> this vote passes with the following +1
>
> Alexandre Vermeerbergen (binding)
> Julien Nioche (binding)
> Richard Zowalla (binding)
>
Hello,
+1 (binding)
Thanks,
Alexandre
Le jeu. 12 oct. 2023 à 10:59, Richard Zowalla a écrit :
>
> Hello all,
>
> This is the 2nd attempt due to an oversight in the components to be
> voted on.
>
> A few weeks ago we conducted a survey [1] and discussed the results
> [2]. Corresponding details
Hello,
+1 (binding)
Thanks,
Alexandre
Le jeu. 12 oct. 2023 à 10:15, Edward Armes a écrit :
>
> -1 (non-binding)
> I would maybe think about keeping JDBC connector and dropping the Redis
> connector as the JDBC connector could potentially include Redis.
>
> Edward
>
> On Thu, 12 Oct 2023,
I agree with Julien.
Le mar. 3 oct. 2023 à 09:20, Julien Nioche
a écrit :
>
> Hi
>
> Thanks Richard. There are some dubious votes indeed.
>
> My views is that we could keep only the modules with 4 votes or more :
> cassandra, elasticsearch, hdfs-*, jms, kafka*, metrics, redis
>
> The rest can be
ransient dependencies for
> compatibility. I didn't check but it might be that some auth libs (from
> hadoop) might rely on javax dependencies causing issues at runtime.
>
> Nothing against a Jira to track.
>
> Gruß
> Richard
>
>
>
> Am 28. September 2023 15:34
Hello,
I noticed we still rely on javax.servlet in storm-server/pom.xml.
Unless I am missing something, Java EE" APIs are supposed to be
deprecated in favor in Jakarta EE APIs.
While I don't know the scope of needed changes in Storm to move to
Jakarta EE APIs, is there any objection if I create
end where eclipse screen showed.
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Friday, September 1, 2023, 8:53 AM, Alexandre Vermeerbergen
> wrote:
>
> And by the way, after copying the changes from STORM-3970 (and closing
> storm-cassandra project, for which I'm antic
And by the way, after copying the changes from STORM-3970 (and closing
storm-cassandra project, for which I'm anticipating low community
interest, so I'm skipping it), I only have 3 errors left in Eclipse
IDE for Storm:
On /storm-client/pom.xml:
line 206 (which just contains tag) error message
23 à 13:30, Bipin Prasad
a écrit :
>
> I will look into this later today.Your project (subproject) jvm shows
> jdk/jvm-11 (as visible in eclipse in Package Explorer window?
> On Thursday, August 31, 2023 at 06:15:55 AM PDT, Alexandre Vermeerbergen
> wrote:
>
> Hello
gt;
> Sent from Yahoo Mail for iPhone
>
>
> On Wednesday, August 30, 2023, 8:19 PM, Alexandre Vermeerbergen
> wrote:
>
> Hello;
>
> I have created a branch in my own fork of storm Github projet, and
> merged Bipin's changes from these two branches on his own fork:
Eclipse locally. If the changes solve the issues, it might be a good
> thing otherwise we need to ensure, Eclipse users have a chance to be
> onboarded :)
>
> Am Dienstag, dem 29.08.2023 um 23:14 -0400 schrieb Alexandre
> Vermeerbergen:
> > Hello Julien,
> >
> > Here's
tion errors, like you do.
>
> Julien
>
>
> On Mon, 28 Aug 2023 at 02:23, Alexandre Vermeerbergen <
> avermeerber...@gmail.com> wrote:
>
> > Hello,
> >
> > I am trying to use my Eclipse IDE to work on a contribution on storm
> > project.
> >
&
Hello,
I am trying to use my Eclipse IDE to work on a contribution on storm project.
I must be missing something, because I though I was just a matter of
using Eclipse's import projects... / Maven / Existing Maven Projects
and point to the root directory of my local Storm git directory.
But
Hello,
I recently created https://issues.apache.org/jira/browse/STORM-3958,
and I realize that this creation is not automatically associated with
a mail to dev@storm.apache.org.
Maybe this is normal, but I'm wondering: aren't we risking to miss
interesting feature requests and/or bug reports if
t; builder and gets published once a new commit is put to that branch ;-)
>
> Am 19. August 2023 22:04:07 MESZ schrieb Alexandre Vermeerbergen
> :
> >I just sent pull request https://github.com/apache/storm-site/pull/45
> >for this change to storm-site.
> >
> >Sinc
. 18 août 2023 à 22:00, Alexandre Vermeerbergen
a écrit :
>
> OK, created https://issues.apache.org/jira/browse/STORM-3957 for the
> tracking (self assigned)
>
> Le ven. 18 août 2023 à 21:48, Richard Zowalla a écrit :
> >
> > I am fine with it.
> >
> > It m
in a release's changelog but might be a
> good thing to know, that someone is working on that task.
>
> Gruß
> Richard
>
> Am Freitag, dem 18.08.2023 um 19:59 +0200 schrieb Alexandre
> Vermeerbergen:
> > Hello,
> >
> > Community/People page on storm-sit
Hello,
Community/People page on storm-site
(https://storm.apache.org/contribute/People.html) is currently
outdated.
For example, it is missing Julien Nioche who recently joined as a PMC.
I volunteer to fix this page, by replacing the static table fed by
_data/committers.yml file, by a link to
Hello Richard,
On the one hand, I have nothing against the use of GitHub issues
instead of JIRA issues. I agree that JIRA is kind of overkill for the
simple need of tracking issues for Storm project.
On the other hand, the migration of existing JIRA issues to GitHub
issues is likely to take
Hello,
Ah sorry: I indeed accepted Richard's invitation to join as a PMC, but I
thought I had to wait for some formal confirmation before I could cast a
binding vote - hence my mention as "non-binding " with my vote.
Should I recast it, or I am right to wait for some formal annouce of my PMC
+1 [non binding]
Alexandre
Le sam. 5 août 2023, 19:24, Bipin Prasad a écrit :
> Note: In order to be compliant with ASF procedures, we need an additional
> vote for Storm 2.5.0 RC4 (which was released yesterday) . Please test the
> following and vote:
>
> Storm Release candidate version 2.5.0
Hello,
So far, +1 [non binding] for 2.5.0 RC4 based on my tests, which are to
use binaries to upgrade my pre production distributed cluster running
10+ topologies at scale (> 1 million tuples per minute) running on
Rocky Linux x64 on AWS EC2 VMs with IBM Semeru JDK 17.0.7.
Since I have been
Hello,
Regarding my tests with Apache Storm 2.5.0 RC2 on a pre-production
cluster at scale, with 10+ topologies, running on RockyLinux 8 with
IBM Semeru 17.0.7 (based on OpenJ9 JVM) on Linux x64, I have detected
no functional regression, not any noticeable performance changes.
On side node, our
253788 0201BF9D
> > > > 92DC24D7 A00FEBAE 809D0F91 EC772FAC C433F16B
> > > > B56F958E 2D2EDF21 0814A02B 58819949 E26B574B
> > > > A75BF1B9
> > > > and change it to:
>
DC24D7A00FEBAE809D0F91EC772FACC433F16BB56F958E2D2EDF210814A02B58819949E26B574BA75BF1B9
> > apache-storm-2.5.0-src.zip
> >
> > and run sha512sum it works.
> >
> > On 2023/07/25 17:13:15 Bipin Prasad wrote:
> > > The sha512 files were generated by "
Hello,
Great !
But I'm facing again an issue with SHA512 validation of the source archive:
wget
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
wget
stream
> dependencies, there were some issues with tests. After this release, we need
> to add jdk11 and 17 to GitHub actions (and then at some point drop jdk8).
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Saturday, July 8, 2023, 11:44 AM, Alexandre Vermeerbergen
> wrote:
Prasad
a écrit :
>
> I am working on release candidate 2, but will also look at this issue this
> weekend and get back to you.Thanks for checking.
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Saturday, July 8, 2023, 1:15 AM, Alexandre Vermeerbergen
> wrote:
&g
Hello,
I tried to check apache-storm-2.5.0.tar.gz.sha512(from
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/),
but I get this error:
$ /usr/bin/sha512sum -c apache-storm-2.5.0.tar.gz.sha512
/usr/bin/sha512sum: apache-storm-2.5.0.tar.gz.sha512: no properly
formatted SHA512
Great news!
I will start testing this Storm 2.5.0 RC later this week, as i do not have
access to my machines before.
Thanks!
Alex
Le mar. 27 juin 2023, 01:15, Bipin Prasad a écrit :
> Storm Release candidate version 2.5.0 rc1 is here:
>
g the committer / pmc circle. CC'ing private@, so we can
> > hopefully get an update.
> >
> > I am asking because I read about the intention to cut a storm 2.5.0
> > release and I am wondering, if we get the necessary votes in a timely
> > manner.
> >
> >
+1 to exclude Storm Cassandra
(my 2 cents)
Thanks,
Alex
Le ven. 16 juin 2023 à 17:58, Bipin Prasad a écrit :
>
> All,
>I am working on creating a new release for Storm 2.5.0. Unfortunately,
> storm-cassandra has been failing tests since we moved to Git Actions. Can
> someone take a look at
+1
Le lun. 12 juin 2023 à 11:57, Richard Zowalla a écrit :
>
> Some weeks passed, any updates?
>
> Gruß
> Richard
>
> Am Donnerstag, dem 11.05.2023 um 19:16 -0400 schrieb P. Taylor Goetz:
> > Thanks for the reminder Richard,
> >
> > In response, I’ve bumped the PMC-private discussion around
Hello,
I just created https://issues.apache.org/jira/browse/STORM-3918
Any objection for this dependency update ?
I guess I can take care of this - I just need a reminder about how to
properly create a git branch to deliver an update to .pom and make
this branch linked to the JIRA
Thanks,
Alex
+1 for whatever makes Apache Storm to be maintained as long as
possible, including my time if needed !
Alexandre
Le ven. 3 févr. 2023 à 14:54, Richard Zowalla a écrit :
>
> Hi all,
>
> I am also +1 for Taylor as PMC and please count me in as well (my first
> comment was a bit vague about it).
>
Hello,
I'd be happy to contribute to Apache Storm in any kind of way.
Just let me know what kind of help I could provide.
Disclaimer: I not skilled in clojure language, so Storm 1.x
maintenance is probably not something I could do efficiently, for I
can help on Java side and on "management" stuff
Hi,
I'm surprised and glad to see a new release on Storm 1.2.x, as I have
still not succeeded in migrating to Storm 2.x.
Not exactly related to this VOTE, but is there some hope to see a
Storm 1.x release which could run with Java 17 LTS ?
Indeed, we currently run our topologies with Storm
+1 congratulations with this new Apache Storm release!
Le sam. 2 nov. 2019 à 10:45, Stig Rohde Døssing
a écrit :
>
> Great job with the release.
>
> Den tor. 31. okt. 2019 kl. 22.48 skrev Ethan Li :
>
> > The Apache Storm community is pleased to announce the release of Apache
> > Storm version
orm 1.2.0+ as well. You can upgrade to
> one of those versions, and update your topologies so they don't use
> deprecated methods. Then the topologies should be compatible with 2.x
> without rebuilding.
>
> Den tir. 24. sep. 2019 kl. 22.34 skrev Alexandre Vermeerbergen <
:
>
> I thought the API changes for Storm 2.x were mostly minor. Which API
> changes are you being blocked by?
>
> Den søn. 22. sep. 2019 kl. 21.27 skrev Alexandre Vermeerbergen <
> avermeerber...@gmail.com>:
>
> > Hello Stig,
> >
> > Thank you very much
ay want to also lobby to get a 1.2.4 release
> out after that.
>
> Den ons. 18. sep. 2019 kl. 17.04 skrev Alexandre Vermeerbergen <
> avermeerber...@gmail.com>:
>
> > Hello,
> >
> > I have seen couple of occurrences of the NullPointerException in Storm
> >
traces seems to tell that the NullPointerException
occurs in some code related to statistics computation, wouldn't it be
better to fix the issue by catching the NullPointerException to avoid
blocking Kafka consumption ?
Kind regards,
Alexandre Vermeerbergen
This is great news (the more PMC members, the more healthly the Apache
Storm project is), welcome Aaron!
Alexandre Vermeerbergen
Le sam. 10 août 2019 à 10:47, Stig Rohde Døssing
a écrit :
>
> I'm happy to announce that Aaron Gresch is now a member of the Storm PMC.
>
> Aaron has
Hello Taylor,
Thank you very much for this Storm 1.2.3 release.
You did a great job to make this process running smoothly for many
releases; and I know that donating one's time on such large project is
a huge contribution.
Whatever you'll do next, may the code with be you!
Alexandre
Le sam. 11 mai 2019 à 19:18, Alexandre Vermeerbergen
a écrit :
>
> +1 (non binding)
>
> - Downloaded binary distribution & used it to update my Storm cloud service
> - Downloaded source distribution, compiled it and used the generated
> .jar files to update my Storm builde
afka brokers), so basically I'm confident to run 1.2.3
final at scale within very short time after it'll be released.
Kind regards,
Alexandre Vermeerbergen
Le ven. 10 mai 2019 à 18:28, P. Taylor Goetz a écrit :
>
> This is a call to vote on releasing Apache Storm 1.2.3 (rc2)
>
> Full
Yes, I am definitely interested first in "Kafka related changes"
because it's the biggest impact I currently have when trying to "port"
my topologies from 1.2.x to 2.x.
The other topics are also very tempting, I think I'll jump to the
"Java port" one as soon it's published..
Storm 2.x's going to
-one error on my part.
>
> The release candidate is still valid. I just need to do an `svn mv`.
>
> Canceling vote to do an svn rename.
>
> -Taylor
>
> > On May 9, 2019, at 3:48 AM, Alexandre Vermeerbergen
> > wrote:
> >
> > Hello,
> >
> >
Hello,
I am confused : there was a mail calling for voting for 1.2.3-RC1 on
8th of January this year.
Is this new call for vote related to exactly the same "code freeze",
or is that a newer code freeze, in which case shouldn't be called
"1.2.3-rc2" ?
Kind regards,
Alexandre V
).getClass();
What would be the migration path from Storm 1.x to Storm 2.x for this
storm-kafka-client dependent class?
Kind regards,
Alexandre Vermeerbergen
Le mer. 1 mai 2019 à 21:18, Stig Rohde Døssing
a écrit :
>
> Yes, we already have a check that the Maven version is above 3.0.0 (
>
(not a blocker for 2.0.0 of course).
How about that?
Kind regards,
Alexandre Vermeerbergen
Le mer. 1 mai 2019 à 19:42, Stig Rohde Døssing
a écrit :
>
> I haven't seen the error you're getting before, but it looks like it's a
> Maven issue, not a Storm issue. Could you try updating to the lat
build-time dependencies?
I also need to know whether or not my BigJars must embed
storm-client.2.0.0.jar (we use to embed storm-core-.jar in
our BigJar)
Kind regards,
Alexandre Vermeerbergen
Le mar. 30 avr. 2019 à 23:49, Roshan Naik
a écrit :
>
> Yes, you need to rebuild your topology
Hello,
I'm eager to test Storm 2.0.0 with my complex topologies, but first of
all: do I need to rebuild all my topologies' Big Jars with Storm
2.0.0, or may I try my existing Storm 1.2.3 (recent snapshot)-based
Big Jars ?
Kind regards,
Alexandre Vermeerbergen
Le mar. 30 avr. 2019 à 00:49, P
Hello Taylor,
+1
DownloadedStorm1.2.3 RC1 + build 1.2.3 RC1 from sources to get up to
date storm-kafka-client
Upgraded by integration cluster with 1.2.3 RC.
Configuration:
- CentOS7, Java 11 from AdoptOpenJDK11.0.1 with Hotspot on all VMs
- 1 Nimbus VM, 7 Supervisor,VMs, 3 Zookeeper VMs, 19
Hello Taylor,
For your information, I have upgraded my "small test cluster" with
this Storm 1.2.3 RC1 and found no regression.
My setup is: Linux CentOS 7, AdoptOpenJDK with HotSpot 11.0.1, 1
Nimbus VM, 1 Supervisor VM, 1 Zookeeper VM, 19 topologies with high
dependency on Storm Kafka Client,
+1
Le sam. 5 janv. 2019 à 14:12, Kishorkumar Patil
a écrit :
>
> +1
>
>
> On Sat, Jan 5, 2019 at 5:04 AM Stig Rohde Døssing
> wrote:
>
> > +1
> >
> > Den lør. 5. jan. 2019 kl. 07.42 skrev Govind Menon <
> > govindappume...@gmail.com>:
> >
> > > +1
> > >
> > > On Jan 4, 2019 23:46, "Roshan Naik"
1 - 100 of 196 matches
Mail list logo
