Thanks all for bringing nice ideas and items to announce and publicize!

Though not a topic for blog, I would like to let us remind the change of
modules (`storm-core` -> `storm-client` and `storm-server`) in release
announcement.

>From Storm 2.0.0, most of the cases end users would need to add only
`storm-client` as a dependency in their topology jar, which greatly reduces
unnecessary dependencies. If my memory is right, there's a case end users
still need to add `storm-server` as a dependency as well - run local
cluster directly instead of storm command - but not sure it is still valid
after we introduced `storm local`.
(Bobby, could you confirm this?)

The way of launching topology in local mode is also changed as well: `storm
local`instead of `storm jar`. The command is documented in storm.py, but
looks like missing in docs/Command-line-client.md so need to add it there.

https://github.com/apache/storm/blob/8a475696e908c53f1c06bf1a8f373d8ac0483427/bin/storm.py#L327-L353

Our strategy on dependency resolution has also changed as well: instead of
shading most of dependencies, we put our best effort to reduce dependencies
for worker (storm-client), and shade only some of dependencies which are
known to be troublesome for version conflict. I guess it's worth to mention
in release announcement too.

https://github.com/apache/storm/blob/8a475696e908c53f1c06bf1a8f373d8ac0483427/shaded-deps/pom.xml#L36-L158

- Jungtaek Lim (HeartSaVioR)

2019년 1월 23일 (수) 오전 4:39, Arun Mahadevan <[email protected]>님이 작성:

> Nice suggestions Roshan and Taylor.
>
> I think we can start with a release announcement (maybe with pointers to
> the docs) and follow it up with blog posts that deep dives into the
> different features and improvements.
>
> A few from my side for the release announcement would be,
>
> - Streams API - A typed API for users to express their streaming
> computations more easily and supports functional style operations. [1]
> - Windowing enhancements and support for window state checkpointing [2]
>
> Would also try to do some write up for blogs around this once we figured
> out how to go about the blog series.
>
> - Arun
>
> [1] https://github.com/apache/storm/blob/master/docs/Stream-API.md
> [2]
>
> https://github.com/apache/storm/blob/master/docs/Windowing.md#stateful-windowing
>
>
>
> On Tue, 22 Jan 2019 at 09:57, P. Taylor Goetz <[email protected]> wrote:
>
> > Awesome. I’ve been thinking about this as well.
> >
> > The release notes don’t really tell the story of everything in this
> > release, and some of the new features and improvements elude my memory.
> >
> > If others could point out new features that they’d like to be pointed out
> > in the release announcement, please list them in this thread. Better yet
> > would be a blurb describing the feature/improvement and what benefits it
> > brings users. Then I can stitch them together into a release
> announcement.
> > Basically crowd/dev-sourcing the release announcement.
> >
> > Or, instead of one big announcement, do we want to do a series of blog
> > posts? If we go the latter route, the first post should probably cover
> the
> > most significant features. What would those be? Roshan has a pretty good
> > start.
> >
> > What would others add?
> >
> > If anyone wants to help out, let me know.
> >
> > -Taylor
> >
> > > On Jan 22, 2019, at 10:37 AM, Bobby Evans <[email protected]> wrote:
> > >
> > > I totally agree, especially with the performance improvements in it.
> > >
> > > Thanks,
> > >
> > > Bobby
> > >
> > > On Tue, Jan 22, 2019 at 12:40 AM Roshan Naik
> > <[email protected]>
> > > wrote:
> > >
> > >> Now that  2.0 has all the votes it needs to move forward, maybe a good
> > >> time to think of some blogs to go with this long awaited release.
> > >> Some potential topics that come to mind are:
> > >> 1- Overview of new features and major changes since 1.x2-
> > Re-architecture
> > >> (messaging, threading, back pressure)3- Micro benchmarks4- Revisit the
> > >> famous Yahoo benchmark5- Window state persistence6- SQL enhancements7-
> > new
> > >> Metrics stuff8- Kafka related changes9- Security10- An area you have
> > worked
> > >> on ?11- Other ideas ?
> > >> Anyone interested in contributing blogs ?
> > >> FYI: I am working on content for topics 2 & 3.
> > >>
> > >> -roshan
> >
> >
>

Reply via email to