Re: Storm 2.0 blogs ?
Taylor, Somewhere in the release notes it would be good to mention the following: - Compatibility: 2.0 is backward compatible with 1.x, but they need to recompile the topo jars. - Dependency changes: Like Alexandre, others are likely to discover the hard way that storm-core is something else now and therefore compilation breaks. -roshan
Re: Storm 2.0 blogs ?
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 such a big change for us, i'm impatient to dig this! Kind regards, Alexandre Le ven. 10 mai 2019 à 18:40, P. Taylor Goetz a écrit : > > I’m going to distill everything mentioned so far into a release announcement > that I hope to get out later today, or more likely, Monday. > > Then we can add follow up blog posts that go into greater detail. > > For reference, I’m reposting the list of topics Roshan came up with: > > 1- Re-architecture - [Roshan] > 2- Windowing enhancements > 3- SQL enhancements > 4- Metrics > 5- Kafka related changes > 6- Security (nimbus admin groups, delegation tokens, optional impersonation) > 7- PMML (Machine Learning) support. > 8- Streams API > 9- Module restructuring & dependency mitigation > 10- Java porting > 11- DRPC cmd line > 12- Lambda support > 13- New spouts: Kinesis & Druid ? > 14- Changes to deployment and cli submission > 15- RAS changes > 16- Trident enhancements > 17- New Admin cmds to debug cluster state > 18 ... others ? > > -Taylor > > > > > > On Jan 29, 2019, at 6:16 PM, Arun M wrote: > > > > Heres a short blurb for Streams API & windowing enhancements. > > > > 1. Streams API > > > > A typed API for expressing streaming computations more easily using > > functional style operations. > > It builds on top of the Storm's core spouts and bolt APIs and automatically > > fuses multiple operations together to optimize the pipeline. > > For more details and examples see - > > https://github.com/apache/storm/blob/master/docs/Stream-API.md > > > > 2. Windowing enhancements > > > > Storm can save/restore the window state to the configured state backend so > > that larger continuous windows can be supported. > > The window boundaries can now be accessed via the APIs. > > For more details see - > > https://github.com/apache/storm/blob/master/docs/Windowing.md#stateful-windowing > > > > Thanks, > > Arun >
Re: Storm 2.0 blogs ?
I’m going to distill everything mentioned so far into a release announcement that I hope to get out later today, or more likely, Monday. Then we can add follow up blog posts that go into greater detail. For reference, I’m reposting the list of topics Roshan came up with: 1- Re-architecture - [Roshan] 2- Windowing enhancements 3- SQL enhancements 4- Metrics 5- Kafka related changes 6- Security (nimbus admin groups, delegation tokens, optional impersonation) 7- PMML (Machine Learning) support. 8- Streams API 9- Module restructuring & dependency mitigation 10- Java porting 11- DRPC cmd line 12- Lambda support 13- New spouts: Kinesis & Druid ? 14- Changes to deployment and cli submission 15- RAS changes 16- Trident enhancements 17- New Admin cmds to debug cluster state 18 ... others ? -Taylor > On Jan 29, 2019, at 6:16 PM, Arun M wrote: > > Heres a short blurb for Streams API & windowing enhancements. > > 1. Streams API > > A typed API for expressing streaming computations more easily using > functional style operations. > It builds on top of the Storm's core spouts and bolt APIs and automatically > fuses multiple operations together to optimize the pipeline. > For more details and examples see - > https://github.com/apache/storm/blob/master/docs/Stream-API.md > > 2. Windowing enhancements > > Storm can save/restore the window state to the configured state backend so > that larger continuous windows can be supported. > The window boundaries can now be accessed via the APIs. > For more details see - > https://github.com/apache/storm/blob/master/docs/Windowing.md#stateful-windowing > > Thanks, > Arun
Re: Storm 2.0 blogs ?
Heres a short blurb for Streams API & windowing enhancements. 1. Streams API A typed API for expressing streaming computations more easily using functional style operations. It builds on top of the Storm's core spouts and bolt APIs and automatically fuses multiple operations together to optimize the pipeline. For more details and examples see - https://github.com/apache/storm/blob/master/docs/Stream-API.md 2. Windowing enhancements Storm can save/restore the window state to the configured state backend so that larger continuous windows can be supported. The window boundaries can now be accessed via the APIs. For more details see - https://github.com/apache/storm/blob/master/docs/Windowing.md#stateful-windowing Thanks, Arun
Re: Storm 2.0 blogs ?
Here is a snippet for the rearchitecture. Keeping it short here as follow up blogs will have more details: 1) New High Performance Core:Storm 2.0 introduces a new core, designed to push boundaries on throughput, latency and energy consumption while maintaining backward compatibility. It features a leaner threading model, a blazing fast messaging subsystem and a lightweight back pressure model. The new engine was motivated by the observation that existing hardware remains capable of performing much better than what the best streaming engines deliver. Storm 2.0 is the first streaming engine capable of breaking the 1 microsecond latency barrier for transfers between two operators. It can sustain very high throughputs and also deliver better energy efficiency. Details on the new architecture and its performance will be covered in upcoming blogs. On Wednesday, January 23, 2019, 10:01:56 AM PST, Stig Rohde Døssing wrote: We should probably also highlight in the release notes that Java 8 is now the minimum. Here is the blurb for storm-kafka-client: # Kafka integration changes ## Removal of storm-kafka The most significant change to Storm's Kafka integration since 1.x, is that storm-kafka has been removed. The module was deprecated a while back, due to Kafka's deprecation of the underlying client library. Users will have to move to the storm-kafka-client module, which uses Kafka's ´kafka-clients´ library for integration. For the most part, the migration to storm-kafka-client is straightforward. The documentation for storm-kafka-client contains a helpful mapping between the old and new spout configurations. If you are using any of the storm-kafka spouts, you will need to migrate offset checkpoints to the new spout, to avoid the new spout starting from scratch on your partitions. You can find a helper tool to do this at https://github.com/apache/storm/tree/master/external/storm-kafka-migration. You should stop your topology, run the migration tool, then redeploy your topology with the storm-kafka-client spout. ## Move to using the KafkaConsumer.assign API Storm-kafka-client in 1.x allowed you to use Kafka's own mechanism to manage which spout tasks were responsible for which partitions. This mechanism was a poor fit for Storm, and was deprecated in 1.2.0. It has been removed entirely in 2.0 https://issues.apache.org/jira/browse/STORM-2542. The storm-kafka-client Subscription interface has also been removed. It offered too limited control over the subscription behavior. It has been replaced with the TopicFilter and ManualPartitioner interfaces. Unless you were using a custom Subscription implementation, this will likely not affect you. If you were using a custom Subscription, the storm-kafka-client documentation describes how to customize assignment https://github.com/apache/storm/blob/master/docs/storm-kafka-client.md#manual-partition-assigment-advanced . ## Other highlights * The KafkaBolt now allows you to specify a callback that will be called when a batch is written to Kafka https://issues.apache.org/jira/browse/STORM-3175. * The FirstPollOffsetStrategy behavior has been made consistent between the non-Trident and Trident spouts. It is now always the case that EARLIEST/LATEST only take effect on topology redeploy, and not when a worker restarts https://issues.apache.org/jira/browse/STORM-2990. * Storm-kafka-client now has a transactional non-opaque Trident spout https://issues.apache.org/jira/browse/STORM-2974. * There is a new examples module for storm-kafka-client at https://github.com/apache/storm/tree/master/examples/storm-kafka-client-examples . * Deprecated methods in KafkaSpoutConfig have been removed. If you are using one of the deprecated methods, check the Javadoc for the latest 1.2.x release, which describes the replacement for each method. Den ons. 23. jan. 2019 kl. 15.54 skrev P. Taylor Goetz : > If you need to format (e.g. code examples, etc.) then markdown is fine. So > is plain text. > > -Taylor > > > On Jan 23, 2019, at 5:24 AM, Stig Rohde Døssing > wrote: > > > > I'll write something for 5 - Kafka related changes. > > > > We have dropped Druid support, so 13 should be only Kinesis. > > > > Which format should the blurbs be written in? (Markdown?) > > > > Den ons. 23. jan. 2019 kl. 08.57 skrev Roshan Naik > > : > > > >> Like Taylor’s suggestion of collectively contributing small blurbs on > >> features for the Release announcement. Thats the first thing people > look on > >> hearing a release announcement. The jira list is not very > understandable at > >> first glance. > >> > >> > >> Based on suggestions so far and a quick scan of the jiras in release > notes > >> here is a draft list in no particular order. I am sure I am missing a > few > >> impt ones. This can be pruned or modified as needed: > >> > >> 1- Re-architecture - [Roshan] > >> 2- Windowing enhancements > >> 3- SQL enhancements > >> 4- Metrics > >> 5- Kafka related changes > >> 6- Security (nimbus
Re: Storm 2.0 blogs ?
We should probably also highlight in the release notes that Java 8 is now the minimum. Here is the blurb for storm-kafka-client: # Kafka integration changes ## Removal of storm-kafka The most significant change to Storm's Kafka integration since 1.x, is that storm-kafka has been removed. The module was deprecated a while back, due to Kafka's deprecation of the underlying client library. Users will have to move to the storm-kafka-client module, which uses Kafka's ´kafka-clients´ library for integration. For the most part, the migration to storm-kafka-client is straightforward. The documentation for storm-kafka-client contains a helpful mapping between the old and new spout configurations. If you are using any of the storm-kafka spouts, you will need to migrate offset checkpoints to the new spout, to avoid the new spout starting from scratch on your partitions. You can find a helper tool to do this at https://github.com/apache/storm/tree/master/external/storm-kafka-migration. You should stop your topology, run the migration tool, then redeploy your topology with the storm-kafka-client spout. ## Move to using the KafkaConsumer.assign API Storm-kafka-client in 1.x allowed you to use Kafka's own mechanism to manage which spout tasks were responsible for which partitions. This mechanism was a poor fit for Storm, and was deprecated in 1.2.0. It has been removed entirely in 2.0 https://issues.apache.org/jira/browse/STORM-2542. The storm-kafka-client Subscription interface has also been removed. It offered too limited control over the subscription behavior. It has been replaced with the TopicFilter and ManualPartitioner interfaces. Unless you were using a custom Subscription implementation, this will likely not affect you. If you were using a custom Subscription, the storm-kafka-client documentation describes how to customize assignment https://github.com/apache/storm/blob/master/docs/storm-kafka-client.md#manual-partition-assigment-advanced . ## Other highlights * The KafkaBolt now allows you to specify a callback that will be called when a batch is written to Kafka https://issues.apache.org/jira/browse/STORM-3175. * The FirstPollOffsetStrategy behavior has been made consistent between the non-Trident and Trident spouts. It is now always the case that EARLIEST/LATEST only take effect on topology redeploy, and not when a worker restarts https://issues.apache.org/jira/browse/STORM-2990. * Storm-kafka-client now has a transactional non-opaque Trident spout https://issues.apache.org/jira/browse/STORM-2974. * There is a new examples module for storm-kafka-client at https://github.com/apache/storm/tree/master/examples/storm-kafka-client-examples . * Deprecated methods in KafkaSpoutConfig have been removed. If you are using one of the deprecated methods, check the Javadoc for the latest 1.2.x release, which describes the replacement for each method. Den ons. 23. jan. 2019 kl. 15.54 skrev P. Taylor Goetz : > If you need to format (e.g. code examples, etc.) then markdown is fine. So > is plain text. > > -Taylor > > > On Jan 23, 2019, at 5:24 AM, Stig Rohde Døssing > wrote: > > > > I'll write something for 5 - Kafka related changes. > > > > We have dropped Druid support, so 13 should be only Kinesis. > > > > Which format should the blurbs be written in? (Markdown?) > > > > Den ons. 23. jan. 2019 kl. 08.57 skrev Roshan Naik > > : > > > >> Like Taylor’s suggestion of collectively contributing small blurbs on > >> features for the Release announcement. Thats the first thing people > look on > >> hearing a release announcement. The jira list is not very > understandable at > >> first glance. > >> > >> > >> Based on suggestions so far and a quick scan of the jiras in release > notes > >> here is a draft list in no particular order. I am sure I am missing a > few > >> impt ones. This can be pruned or modified as needed: > >> > >> 1- Re-architecture - [Roshan] > >> 2- Windowing enhancements > >> 3- SQL enhancements > >> 4- Metrics > >> 5- Kafka related changes > >> 6- Security (nimbus admin groups, delegation tokens, optional > >> impersonation) > >> 7- PMML (Machine Learning) support. > >> 8- Streams API > >> 9- Module restructuring & dependency mitigation > >> 10- Java porting > >> 11- DRPC cmd line > >> 12- Lambda support > >> 13- New spouts: Kinesis & Druid ? > >> 14- Changes to deployment and cli submission > >> 15- RAS changes > >> 16- Trident enhancements > >> 17- New Admin cmds to debug cluster state > >> 18 ... others ? > >> > >> Please pick the topics you can contribute blurbs for. I have put my name > >> against one. It will help Taylor aggregate them and do the necessary > final > >> edits. > >> > >> > >> -Roshan > >> > >> > >> > >> > >> > >
Re: Storm 2.0 blogs ?
If you need to format (e.g. code examples, etc.) then markdown is fine. So is plain text. -Taylor > On Jan 23, 2019, at 5:24 AM, Stig Rohde Døssing > wrote: > > I'll write something for 5 - Kafka related changes. > > We have dropped Druid support, so 13 should be only Kinesis. > > Which format should the blurbs be written in? (Markdown?) > > Den ons. 23. jan. 2019 kl. 08.57 skrev Roshan Naik > : > >> Like Taylor’s suggestion of collectively contributing small blurbs on >> features for the Release announcement. Thats the first thing people look on >> hearing a release announcement. The jira list is not very understandable at >> first glance. >> >> >> Based on suggestions so far and a quick scan of the jiras in release notes >> here is a draft list in no particular order. I am sure I am missing a few >> impt ones. This can be pruned or modified as needed: >> >> 1- Re-architecture - [Roshan] >> 2- Windowing enhancements >> 3- SQL enhancements >> 4- Metrics >> 5- Kafka related changes >> 6- Security (nimbus admin groups, delegation tokens, optional >> impersonation) >> 7- PMML (Machine Learning) support. >> 8- Streams API >> 9- Module restructuring & dependency mitigation >> 10- Java porting >> 11- DRPC cmd line >> 12- Lambda support >> 13- New spouts: Kinesis & Druid ? >> 14- Changes to deployment and cli submission >> 15- RAS changes >> 16- Trident enhancements >> 17- New Admin cmds to debug cluster state >> 18 ... others ? >> >> Please pick the topics you can contribute blurbs for. I have put my name >> against one. It will help Taylor aggregate them and do the necessary final >> edits. >> >> >> -Roshan >> >> >> >> >> signature.asc Description: Message signed with OpenPGP
Re: Storm 2.0 blogs ?
I'll write something for 5 - Kafka related changes. We have dropped Druid support, so 13 should be only Kinesis. Which format should the blurbs be written in? (Markdown?) Den ons. 23. jan. 2019 kl. 08.57 skrev Roshan Naik : > Like Taylor’s suggestion of collectively contributing small blurbs on > features for the Release announcement. Thats the first thing people look on > hearing a release announcement. The jira list is not very understandable at > first glance. > > > Based on suggestions so far and a quick scan of the jiras in release notes > here is a draft list in no particular order. I am sure I am missing a few > impt ones. This can be pruned or modified as needed: > > 1- Re-architecture - [Roshan] > 2- Windowing enhancements > 3- SQL enhancements > 4- Metrics > 5- Kafka related changes > 6- Security (nimbus admin groups, delegation tokens, optional > impersonation) > 7- PMML (Machine Learning) support. > 8- Streams API > 9- Module restructuring & dependency mitigation > 10- Java porting > 11- DRPC cmd line > 12- Lambda support > 13- New spouts: Kinesis & Druid ? > 14- Changes to deployment and cli submission > 15- RAS changes > 16- Trident enhancements > 17- New Admin cmds to debug cluster state > 18 ... others ? > > Please pick the topics you can contribute blurbs for. I have put my name > against one. It will help Taylor aggregate them and do the necessary final > edits. > > > -Roshan > > > > >
Re: Storm 2.0 blogs ?
Like Taylor’s suggestion of collectively contributing small blurbs on features for the Release announcement. Thats the first thing people look on hearing a release announcement. The jira list is not very understandable at first glance. Based on suggestions so far and a quick scan of the jiras in release notes here is a draft list in no particular order. I am sure I am missing a few impt ones. This can be pruned or modified as needed: 1- Re-architecture - [Roshan] 2- Windowing enhancements 3- SQL enhancements 4- Metrics 5- Kafka related changes 6- Security (nimbus admin groups, delegation tokens, optional impersonation) 7- PMML (Machine Learning) support. 8- Streams API 9- Module restructuring & dependency mitigation 10- Java porting 11- DRPC cmd line 12- Lambda support 13- New spouts: Kinesis & Druid ? 14- Changes to deployment and cli submission 15- RAS changes 16- Trident enhancements 17- New Admin cmds to debug cluster state 18 ... others ? Please pick the topics you can contribute blurbs for. I have put my name against one. It will help Taylor aggregate them and do the necessary final edits. -Roshan
Re: Storm 2.0 blogs ?
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 님이 작성: > 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 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 wrote: > > > > > > I totally agree, especially with the performance improvements in it. > > > > > > Thanks, > > > > > > Bobby > > > > > > On Tue, Jan 22, 2019 at 12:40 AM Roshan Naik > > > > > 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 > > > > >
Re: Storm 2.0 blogs ?
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 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 wrote: > > > > I totally agree, especially with the performance improvements in it. > > > > Thanks, > > > > Bobby > > > > On Tue, Jan 22, 2019 at 12:40 AM Roshan Naik > > > 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 > >
Re: Storm 2.0 blogs ?
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 wrote: > > I totally agree, especially with the performance improvements in it. > > Thanks, > > Bobby > > On Tue, Jan 22, 2019 at 12:40 AM Roshan Naik > 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 signature.asc Description: Message signed with OpenPGP
Re: Storm 2.0 blogs ?
+1 Another interesting topic is PMML (Machine Learning) support. Hugo > On Jan 22, 2019, at 7:37 AM, Bobby Evans wrote: > > I totally agree, especially with the performance improvements in it. > > Thanks, > > Bobby > > On Tue, Jan 22, 2019 at 12:40 AM Roshan Naik > 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
Re: Storm 2.0 blogs ?
I totally agree, especially with the performance improvements in it. Thanks, Bobby On Tue, Jan 22, 2019 at 12:40 AM Roshan Naik 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
Storm 2.0 blogs ?
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
