Yes, your reasoning is correct. The topology is overriding the debug configurations, Storm allows topology to override all of the topology specific settings.
On Fri, Dec 2, 2016 at 3:41 AM, Mostafa Gomaa <[email protected]> wrote: > I think nimbus configuration is what you have on your nimbus machine, > "topology.debug" was set to false over there. Topology config are config > values that start with the "topology." prefix in the yaml file. Your code > was overriding the debug setting for the topology, so you were seeing two > different values. I'm not too sure if my reasoning is correct though. > > On Dec 2, 2016 1:33 PM, "Ohad Edelstein" <[email protected]> wrote: > >> I am embarrassed to say that you are right… thanks! >> But what is the difference between the two? >> Thanks >> >> From: Mostafa Gomaa <[email protected]> >> Reply-To: "[email protected]" <[email protected]> >> Date: Friday, 2 December 2016 at 13:03 >> To: "[email protected]" <[email protected]> >> Cc: "[email protected]" <[email protected]> >> Subject: Re: topology.debug always true >> >> Are you sure you're not overriding this configuration in code when >> building the topology? >> >> On Dec 1, 2016 10:07 PM, "Ohad Edelstein" <[email protected]> wrote: >> >>> We see that the topology.debug set to two different values: >>> >>> And: >>> We set the topology.debug to false ( we know its set that way to default >>> but we thought that, this was the problem ). >>> Is there a different meaning to the param in this two screens? >>> >>> >>>
