Config.TOPOLOGY_ACKERS property

[Srividhya Shanmugam <Sr...@fico.com>]

Several documents refer to "Config.TOPOLOGY_ACKERS" property in the storm's config class. But the source code does not list this property. Also the defaults.yaml file that come with storm's download does not have this property too. Instead there is a different property "topology.ackers.executors" in the config class. I have been using topology.ackers.executors" to test the ackers functionality.

Are both same? Or should documentation reflect the new one?

Thanks!

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.

Re: Config.TOPOLOGY_ACKERS property

[Chi Hoang <ch...@groupon.com>]

I think you are getting confused.

The API constant name:
http://storm.apache.org/javadoc/apidocs/backtype/storm/Config.html#TOPOLOGY_ACKER_EXECUTORS

That constant represents a property value:
http://storm.apache.org/javadoc/apidocs/constant-values.html#backtype.storm.Config.TOPOLOGY_ACKER_EXECUTORS

They refer to the same thing in that you can:
property.get(Config.TOPOLOGY_ACKER_EXECUTORS)
or
property.get("topology.acker.executors")

On Tue, Apr 14, 2015 at 7:01 AM, Srividhya Shanmugam <
SrividhyaShanmugam@fico.com> wrote:

>  Several documents refer to “Config.TOPOLOGY_ACKERS” property in the
> storm’s config class. But the source code does not list this property. Also
> the defaults.yaml file that come with storm’s download does not have this
> property too. Instead there is a different property
> “topology.ackers.executors” in the config class. I have been using
> topology.ackers.executors” to test the ackers functionality.
>
>
>
> Are both same? Or should documentation reflect the new one?
>
>
>
> Thanks!
>
> This email and any files transmitted with it are confidential, proprietary
> and intended solely for the individual or entity to whom they are
> addressed. If you have received this email in error please delete it
> immediately.
>