Re: Recording - Storm & Kafka Meetup on April 20th 2017
Thank you for posting On Fri, Apr 21, 2017 at 9:08 PM, Roshan Naikwrote: > It was a great meetup and for the benefit of those interested but unable > to attend it, here is a link to the recording : > > > > https://www.youtube.com/watch?v=kCRv6iEd7Ow > > > > List of Talks: > > - *Introduction* – Suresh Srinivas (Hortonworks) > > - [4m:31sec] – *Overview of Storm 1.1* - Hugo Louro > (Hortonworks) > > - [20m] – *Rethinking the Storm 2.0 Worker* - Roshan Naik > (Hortonworks) > > - [57m] – *Storm in Retail Context: Catalog data processing > using Kafka, Storm & Microservices* - Karthik Deivasigamani (WalMart > Labs) > > - [1h: 54m:45sec] *– Schema Registry & Streaming Analytics > Manager (aka StreamLine) *- Sriharsha Chintalapani (Hortonworks) > > > > >
Recording - Storm & Kafka Meetup on April 20th 2017
It was a great meetup and for the benefit of those interested but unable to attend it, here is a link to the recording : https://www.youtube.com/watch?v=kCRv6iEd7Ow List of Talks: - Introduction – Suresh Srinivas (Hortonworks) - [4m:31sec] – Overview of Storm 1.1 - Hugo Louro (Hortonworks) - [20m] – Rethinking the Storm 2.0 Worker - Roshan Naik (Hortonworks) - [57m] – Storm in Retail Context: Catalog data processing using Kafka, Storm & Microservices - Karthik Deivasigamani (WalMart Labs) - [1h: 54m:45sec] – Schema Registry & Streaming Analytics Manager (aka StreamLine) - Sriharsha Chintalapani (Hortonworks)
[GitHub] storm pull request #2082: expose Tuple
GitHub user daluu opened a pull request: https://github.com/apache/storm/pull/2082 expose Tuple in case people have uses for it, like in unit testing for example (that's what I was using it for) You can merge this pull request into a Git repository by running: $ git pull https://github.com/daluu/storm master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/storm/pull/2082.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2082 commit f6f4ac7dfbf351ea1c91b0a1a9404213706ed950 Author: David LuuDate: 2017-04-21T21:31:55Z expose Tuple in case people have uses for it, like in unit testing for example --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] storm pull request #2081: [STORM-2482] Refactor the Storm auto credential pl...
GitHub user arunmahadevan opened a pull request: https://github.com/apache/storm/pull/2081 [STORM-2482] Refactor the Storm auto credential plugins to be more usable 1. Create a new storm module storm-autocreds 2. Move AutoHDFS and AutoHBase to storm-autocreds 3. Refactor code and accepts config keys for customizing the hadoop configuration for the plugins 4. Package the auto cred and dependency jars in the storm binary and deploy to lib-autocreds You can merge this pull request into a Git repository by running: $ git pull https://github.com/arunmahadevan/storm STORM-2482-1.x Alternatively you can review and apply these changes as the patch at: https://github.com/apache/storm/pull/2081.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2081 commit aa2fe29982cd688f425568a75281048aa92aca7b Author: Arun MahadevanDate: 2017-04-18T07:59:56Z [STORM-2482] Refactor the Storm auto credential plugins to be more usable 1. Create a new storm module storm-autocreds 2. Move AutoHDFS and AutoHBase to storm-autocreds 3. Refactor code and accepts config keys for customizing the hadoop configuration for the plugins 4. Package the auto cred and dependency jars in the storm binary and deploy to lib-autocreds --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---