Re: [ANNOUNCE] New Storm Commiter/PMC Member: Xin Wang

2016-11-30 Thread Matthias J. Sax
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Congrats!

On 11/30/16 9:05 PM, Eranga Heshan wrote:
> Congratulations Xin Wang. 😃 Hope to see you on mailing list soon.
> 
> Cheers, Regards,
> 
> 
>  Eranga Heshan /Undergraduate/ Computer Science & Engineering 
> University of Moratuwa Mobile:+94 71 138 2686
>  Email:  era...@wso2.com
>  
> 
> 
> 
> 
> 
> On Thu, Dec 1, 2016 at 10:13 AM, Jungtaek Lim  > wrote:
> 
> Please join me in welcoming Xin Wang as a new Apache Storm
> Committer and PMC member.
> 
> Xin Wang has showed strong commitment to the Apache Storm
> community via code contributions for a long time spanning both core
> and as well as integration components. He also has showed active 
> participation on mailing lists.
> 
> Congratulations and welcome Xin!
> 
> - Jungtaek Lim (HeartSaVioR)
> 
> 
-BEGIN PGP SIGNATURE-
Comment: GPGTools - https://gpgtools.org

iQIYBAEBCgAGBQJYP7PKAAoJELz8Z8hxAGOi1O4P31n7hF15LhI7pGzfXqBxXuH3
UMPlz3nPCfgHxGSnPCxP+P/eDadoTqt22/U49bFI7SJepOmIoC+zk5w1LaEZp9M2
LUrgc+PVRoBkpWUtLlXtuFvXi3plUz1bksVivTVxgM6EoHNHa7Gto5RNlAQH3BDV
bJit6XEt1eW9ejiKQTcIBnDxwA08iur5e01rZVLDzTRtBglqv0qquW7W6S904onL
QPa4ZWfkPOtFIMSf6mq4Eaq4n/i46kdpOF7SH6xqo/OTsIQ/ZKIMliTcgwnTUtFe
WErMuVJWsaBIgrwSpfvpvuKSXiFUjYSVYK+92ROnGef6Aw1VjtXnlMZxnjpBNN8u
frywK3UVdBnNRNNj5uNZL/FdjGcHv4E7as8xxRWCV40HBQtoSIIcBbgXqT264Ioj
48x3YFKwB887+n/VIt9ea/KdaHT/KKMWzIVuOIzgzLsRx7lZRR4bV7UlDDWhpg+R
AGO51w6bTRcjvyp6w1E7pJ2zmaoi27qxiXNXWZUBwLBaAw/tIRk8jpT3A8pwneOn
+26SaN84+5D+tTDx8yjNqvV8tuSwGP2eNGiBTMHuJn67T+83s56A3CZxfmCcTnuF
YNs/BZ9R7J61h3KjvxcR8L38pDfwyXHBUV2LOb2D2e2JKmuxmPPaD8i/68WjDNda
LztW1lTj5GkoZ6M=
=WrHr
-END PGP SIGNATURE-


Re: Does the bolt in between have the ability to re-emit a failed tuple?

2016-11-30 Thread Navin Ipe
Apart from the previous question, there's also the question of whether we
should ack the tuple in execute() of Bolt1? Or is it just sufficient to ack
it in Bolt2?


On Wed, Nov 30, 2016 at 12:28 PM, Navin Ipe  wrote:

> Hi,
>
> Just need a confirmation for this topology:
>
> *Spout* ---emit---> *Bolt1* ---emit---> *Bolt2*
>
> Spout is BaseRichSpout. Bolt1 and Bolt2 are BaseRichBolt.
> Spout emits just one tuple per nextTuple() call.
> Bolt1 anchors to the tuple it received from Spout and emits many different
> tuple objects.
>
> If any of the emits of Bolt1 fails, is there no way for Bolt 1 to re-emit
> the tuple? Do I have to wait for the topology to figure out that one of
> Bolt1's tuples failed and then do a re-emit from the Spout?
>
> --
> Regards,
> Navin
>



-- 
Regards,
Navin


Re: [ANNOUNCE] New Storm Commiter/PMC Member: Xin Wang

2016-11-30 Thread Eranga Heshan
Congratulations Xin Wang. 😃 Hope to see you on mailing list soon.

Cheers,
Regards,


Eranga Heshan
*Undergraduate*
Computer Science & Engineering
University of Moratuwa
Mobile:  +94 71 138 2686 <%2B94%2071%20552%202087>
Email: era...@wso2.com 
   
   

On Thu, Dec 1, 2016 at 10:13 AM, Jungtaek Lim  wrote:

> Please join me in welcoming Xin Wang as a new Apache Storm Committer and
> PMC member.
>
> Xin Wang has showed strong commitment to the Apache Storm community via
> code contributions for a long time spanning both core and as well as
> integration components. He also has showed active participation on
> mailing lists.
>
> Congratulations and welcome Xin!
>
> - Jungtaek Lim (HeartSaVioR)
>


[ANNOUNCE] New Storm Commiter/PMC Member: Xin Wang

2016-11-30 Thread Jungtaek Lim
Please join me in welcoming Xin Wang as a new Apache Storm Committer and
PMC member.

Xin Wang has showed strong commitment to the Apache Storm community via
code contributions for a long time spanning both core and as well as
integration components. He also has showed active participation on mailing
lists.

Congratulations and welcome Xin!

- Jungtaek Lim (HeartSaVioR)


Clarity on external/storm-kafka-client

2016-11-30 Thread Kristopher Kane
I need some clarification on Kafka broker version support across Storm
branches.

storm-kafka-client uses the 'new' Kafka APIs


The master branch README of storm-kafka-client says that it ONLY supports
Kafka version .10 and later.

The 1.x branch README of storm-kafka-client says that it ONLY supports
Kafka version .10 and later.

The 1.0.x branch README of storm-kafka-client says that it ONLY supports
Kafka version .9 and later.


Is it really true that 1.x and later only support Kafka version .10 and
later or that it was tested on Kafka .10 but since it is the new API really
still works on .9 as well  and the wording was never changed in the README?

Thanks,

Kris


Save the date: ApacheCon Miami, May 15-19, 2017

2016-11-30 Thread Rich Bowen
Dear Apache enthusiast,

ApacheCon and Apache Big Data will be held at the Intercontinental in
Miami, Florida, May 16-18, 2017. Submit your talks, and register, at
http://apachecon.com/  Talks aimed at the Big Data section of the event
should go to
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp
while other talks should go to
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp


ApacheCon is the best place to meet the people that develop the software
that you use and rely on. It’s also a great opportunity to deepen your
involvement in the project, and perhaps make the leap to contributing.
And we find that user case studies, showcasing how you use Apache
projects to solve real world problems, are very popular at this event.
So, do consider whether you have a use case that might make a good
presentation.

ApacheCon will have many different ways that you can participate:

Technical Content: We’ll have three days of technical sessions covering
many of the projects at the ASF. We’ll be publishing a schedule of talks
on March 9th, so that you can plan what you’ll be attending

BarCamp: The Apache BarCamp is a standard feature of ApacheCon - an
un-conference style event, where the schedule is determined on-site by
the attendees, and anything is fair game.

Lightning Talks: Even if you don’t give a full-length talk, the
Lightning Talks are five minute presentations on any topic related to
the ASF, and can be given by any attendee. If there’s something you’re
passionate about, consider giving a Lightning Talk.

Sponsor: It costs money to put on a conference, and this is a great
opportunity for companies involved in Apache projects, or who benefit
from Apache code - your employers - to get their name and products in
front of the community. Sponsors can start any any monetary level, and
can sponsor everything from the conference badge lanyard, through larger
items such as video recordings and evening events. For more information
on sponsoring ApacheCon, see http://apachecon.com/sponsor/

So, get your tickets today at http://apachecon.com/ and submit your
talks. ApacheCon Miami is going to be our best ApacheCon yet, and you,
and your project, can’t afford to miss it.

-- 
Rich Bowen - rbo...@apache.org
VP, Conferences
http://apachecon.com
@apachecon



Re: moving from storm 0.9.3 to storm 1.0.1

2016-11-30 Thread Xin Wang
Hi Ohad,

You can try setting topology.backpressure.enable: false

-Xin Wang (vesense)

2016-11-30 17:58 GMT+08:00 Ohad Edelstein :

> We are in the process of upgrading our storm infra from 0.9.3 to 1.0.1
> We are running python in the storm.
> We moved for the upgrade from ubuntu14.04 to ubuntu16.04
>
> What we are seeing are very disappointing results,
> Out of the box, with about the same basic params set, we see slowness in
> the new version of about 2%.
> Where we hopped to see an increase of some sort.
> Any ideas with what we can tweak?
> Thanks
>
>


moving from storm 0.9.3 to storm 1.0.1

2016-11-30 Thread Ohad Edelstein
We are in the process of upgrading our storm infra from 0.9.3 to 1.0.1
We are running python in the storm.
We moved for the upgrade from ubuntu14.04 to ubuntu16.04

What we are seeing are very disappointing results,
Out of the box, with about the same basic params set, we see slowness in the 
new version of about 2%.
Where we hopped to see an increase of some sort.
Any ideas with what we can tweak?
Thanks