You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Dave Barnes <db...@pivotal.io> on 2015/10/21 20:22:35 UTC
GEODE-188 Gfsh uses the wrong name for the gateway substitution
filter in 'create async-event-queue' command
GEODE-188 has been fixed in code, so I'd like to update the docs.
The code fix was to replace "gateway-event-substitution-listener" with "
gateway-event-substitution-filter".
My questions:
1. Can someone please explain the purpose of gateway-event-substitution-filter?
I need to add a definition to the cache.xml documentation.
2. Is gateway-event-substitution-listener also a valid setting, which was
simply out of place in this case, or is it a totally bogus name? If valid,
can someone please explain this as well, so I can create a definition for
cache.xml purposes?
Thanks,
Dave Barnes
Sr. Content Dev, Pivotal
Re: GEODE-188 Gfsh uses the wrong name for the gateway substitution
filter in 'create async-event-queue' command
Posted by Dave Barnes <db...@pivotal.io>.
Following up with info provided by Dan Smith, and another question for the
community:
Answer to (1.):
Comment for Interface GatewayEventSubstitutionFilter: ..."provides a
way to specify
a substitute value to be stored in the GatewayQueueEvent and enqueued in
the RegionQueue."
Answer to (2.):
The attribute gateway-event-substitution-listener does not exist.
Followup question:
Under what circumstances would a person want to use this capability -- that
is, why slip a substitute value into the gateway event queue?
Thanks,
-Dave
On Wed, Oct 21, 2015 at 11:22 AM, Dave Barnes <db...@pivotal.io> wrote:
> GEODE-188 has been fixed in code, so I'd like to update the docs.
> The code fix was to replace "gateway-event-substitution-listener" with "
> gateway-event-substitution-filter".
> My questions:
> 1. Can someone please explain the purpose of gateway-event-substitution-filter?
> I need to add a definition to the cache.xml documentation.
> 2. Is gateway-event-substitution-listener also a valid setting, which was
> simply out of place in this case, or is it a totally bogus name? If valid,
> can someone please explain this as well, so I can create a definition for
> cache.xml purposes?
> Thanks,
> Dave Barnes
> Sr. Content Dev, Pivotal
>