Re: [DISCUSS] TTL setting on WAN

2019-03-25 Thread Suranjan Kumar
Hi, I think the one approach for a user would be to 'filter' the events while dispatching. If I remember correctly, we can attach a filter at dispatch time and filter the events based on creationTime of the GatewayEvent. We can provide a pre created filter and use it based on some so that user doe

apply for the edit permission of Geode Jira

2019-03-25 Thread Gang Yan
Hi Geode Dev could you help me to get edit permission of Geode Jira? Thanks and regards Gang Yan(闫钢) GemFire product management team, Beaverton g...@pivotal.io

Re: [DISCUSS] TTL setting on WAN

2019-03-25 Thread Bruce Schuchardt
I've walked through the code to forward expiration actions to async event listeners & don't see how to apply it to removal of queue entries for WAN.  The current implementation just queues the expiration actions.  If we wanted to remove any queued events associated with the expired region entry

Copying pdx types via client

2019-03-25 Thread Michael Stolz
Does this functionality exist in the Native Client as well as the Java Client? -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771

Re: release/1.9.0 branch has been re-cut

2019-03-25 Thread Sai Boorlagadda
I have updated JIRA tickets to 1.9.0 as in "update fixVersion = '1.9.0' where fixVersion = '1.10.0' AND status in (closed, resolved)" On Mon, Mar 25, 2019 at 8:49 AM Sai Boorlagadda wrote: > Hello Everyone, > > As discussed in other email thread I have re-cut a new release branch for > Apache G

release/1.9.0 branch has been re-cut

2019-03-25 Thread Sai Boorlagadda
Hello Everyone, As discussed in other email thread I have re-cut a new release branch for Apache Geode 1.9.0 - "release/1.9.0" off of sha "ec5a24b78c51b6a29b8bf656f91004d09510d244". We already have an existing pipeline for 1.9.0[1], So I will rename the current release branch as "release/1.9.0-o

Re: [DISCUSS] Proposal to re-cut Geode 1.9.0 release branch

2019-03-25 Thread Sai Boorlagadda
Thanks Owen. I am going to re-cut the branch for 1.9.0 and request community to do the sanity check for the new branch. On Fri, Mar 22, 2019 at 4:24 PM Owen Nichols wrote: > @Sai, this discussion has received no objections and enough +1’s to > proceed with re-cutting the release 1.9.0 branch. >