Ooops... just missed it... my +1 as well
Just finished verifying the foll:- spun up local cluster with binary dist-
checked single a 2 worker modes. with and without ackers in each mode- ran
SimplifiedWordCountTopo- did some quick perf verifications with
ConstSpoutNullBolt- basic checking of
Wow. This is a special occasion…
The 2.0 release has been a very long time in the making, I can’t begin to thank
all those who helped shepherd this branch to release quality.
To me this is an Apache project at it’s finest. We’ve seen core contributors
come and go. And when they go, we’ve seen
Yeah, I had an expiration date on now of my keys. I’ve sorted it out, but need
to wait for propagation of myyl keys.
This is currently blocking the 1.2.x. and 1.1.x releases. But it looks like we
can move forward with the 2.0.0 release.
-Taylor
> On May 2, 2019, at 4:51 PM, Ethan Li wrote:
>
+1
1. Checked *.asc, *.md5, *.sha512
2. Built from the source code and ran unit tests; created a storm distribution
based on it
3. set up a standalone cluster (based on apache-storm-2.0.0.zip,
apache-storm-2.0.0.tar.gz, the storm distribution created above, separately)
4. Launched
Subscription has been replaced with TopicFilter. Subscription isn't
deprecated in 1.x because it is not possible to backport TopicFilter
without breaking changes. The replacement is the TopicFilter and
ManualPartitioner classes.
getKey/ValueDeserializer is deprecated in the latest 1.x release,
Hello,
Thanks, and my step issue with Storm 2.0.0 is with some Storm Kafka
Client breaking changes in KafkaSpoutConfig class.
See attached source for our homebrewed BasicKafkaSpout, I have at
least the following compilation errors:
> we can just bump it to something like 3.5.0. I'll raise an issue for it.
+1 and Thanks Alexandre for finding this, it is a help.
On Wed, May 1, 2019 at 2:18 PM Stig Rohde Døssing
wrote:
> Yes, we already have a check that the Maven version is above 3.0.0 (
>
Yes, we already have a check that the Maven version is above 3.0.0 (
https://github.com/apache/storm/blob/master/pom.xml#L1439), IMO we can just
bump it to something like 3.5.0. I'll raise an issue for it.
Den ons. 1. maj 2019 kl. 20.59 skrev Alexandre Vermeerbergen <
avermeerber...@gmail.com>:
Hello Stig,
Good catch: I upgraded Maven to version 3.6.1 and I rebuilt everything
from source tar.gz without any trouble.
So I delay my vote and I'm no longer blocked since I have
storm-kafka-client-2.0.0.jar allowing me to rebuilt my topologies.
Just a question: since my experience showed
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 latest Maven
version?
Den ons. 1. maj 2019 kl. 19.30 skrev Alexandre Vermeerbergen <
avermeerber...@gmail.com>:
> Hello,
>
> I don't know if this is worth a -1
Alexandre,
I think we tend to assume people use a dependency management tool:
https://storm.apache.org/releases/2.0.0-SNAPSHOT/Maven.html
The easiest way for you to get a list of the jars that need to be on the
classpath is to make a dummy Maven project, add the snippet I linked to the
POM, and
Hello,
I tried to rebuild my topologies with 2.0, but I hit a first trivial
issue: I used to rely on storm-core-.jar in our classpath to
resolve Storm API dependencies, but storm-core-2.0.0.jar doesn't seem
to contain anymore classes like org.apache.storm.task.OutputCollector
which is used in our
+1
- Downloaded binaries
- Brought up a local cluster
- Ran a few topologies and checked the output and logs.
If I just click on the "Owner" link from the UI, it displays a red banner
with a warning.
"This user's topologies are in danger of being unscheduled due to the
owner's over-use of cluster
Yes, you need to rebuild your topology jars against 2.0.
If you have some settings to tweak perf with 1.x, refer to
https://github.com/apache/storm/blob/master/docs/Performance.md for the 2.x
configs.
On Tuesday, April 30, 2019, 2:41:49 PM PDT, Alexandre Vermeerbergen
wrote:
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.
+1 (binding)
> source
- verify file (MD5, SHA)
-- source, tar.gz : OK
-- source, zip : OK
- extract file
-- source, tar.gz : OK
-- source, zip : OK
- diff-ing extracted files between tar.gz and zip : OK
- build source with JDK 8
-- source, tar.gz : OK
- build source dist
-- source, tar.gz :
Built from the source code. All Unit tests passed.
Ran some basic tests with WordCountTopology, BasicDRPCTopology.
Run ThroughputVsLatency for comparison and it looks good- with 99.9% of
events processed within 5.4ms.
+1
On Tue, Apr 30, 2019 at 2:16 PM Derek Dagit wrote:
> OK ran the
+1
Ran tests from source zip
Installed and ran ExclamationTopology on single-node cluster from binary zip
Verified no unexpected error logs.
Clicked around a bit in UI, verified that logviewer works.
Checked out tag and ran the license check plugin to generate
DEPENDENCY-LICENSES. Verified that
OK ran the distribution from the tarball, and built and ran from the src
tarball on macOS with JDK8. Tested WordCountTopology on both and it seemed
fine.
+1
On Tue, Apr 30, 2019 at 11:55 AM Derek Dagit wrote:
> Sent too soon:
>
> - I verified sigs and sums
> - Built the source from the tarball
Sent too soon:
- I verified sigs and sums
- Built the source from the tarball on macOS
- I saw a couple of test errors because the local stormconf.ser was gone
when the supervisor tried to open it, and this resulted in a crash. I
re-ran the tests and they passed.
- I do not think this is a
- I verified sigs and sums
On Mon, Apr 29, 2019 at 5:49 PM P. Taylor Goetz wrote:
> This is a call to vote on releasing Apache Storm 2.0.0 (rc7)
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/RELEASE_NOTES.html
>
> The
This is a call to vote on releasing Apache Storm 2.0.0 (rc7)
Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/RELEASE_NOTES.html
The tag/commit to be voted upon is v2.0.0:
22 matches
Mail list logo
