Re: Is topology.tick.tuple.freq.secs a topology-level or component-level setting?

2016-10-31 Thread Matt Foley
Thanks, Taylor.  To confirm, if you set it at the component level, then different components in the SAME topology can have different frequencies of tick tuple? Thanks, --Matt From: "P. Taylor Goetz" Reply-To: Date: Monday, October 31, 2016 at 2:07 PM To: Subject: Re: Is topology.tick.

Re: Is topology.tick.tuple.freq.secs a topology-level or component-level setting?

2016-10-31 Thread P. Taylor Goetz
Hi Matt, It depends on where/how you set it: storm.yaml—> cluster wide topology conf. —> topology wide getComponentConfiguration —> component specific If you want to control it at the component level, leave it out of the storm.yaml and topology configuration. -Taylor > On Oct 31, 2016, at 2:

Is topology.tick.tuple.freq.secs a topology-level or component-level setting?

2016-10-31 Thread Matt Foley
Hi, There is ambiguity in the available documentation: The name “topology.tick.tuple.freq.secs” implies it is topology-level. But it is clearly set at the component level, in Bolt::getComponentConfiguration() method. At which level does it take effect? The primary example blog at http