I never knew there was a Region expiration that destroyed the whole region. Wow! Live and learn.
-- Mike Stolz Principal Engineer, Pivotal Cloud Cache Mobile: +1-631-835-4771 On Tue, Sep 10, 2019 at 12:48 PM Darrel Schneider <[email protected]> wrote: > *@dschneider-pivotal* requested changes on this pull request. > > I think the original ticket is wrong. When "region" expiration happens, > and the action is destroy, it actually does destroy the region. It > basically calls either Region.destroyRegion or Region.localDestroyRegion. > Both of these blow away the entries AND the region. > If the "region" expiration action is invalidate, then that leaves the > region in place and only invalidates the entries (just like > Region.invalidateRegion and Region.localInvalidateRegion). I think you want > to stress that when a region expiration action triggers, it is applied to > the region as a whole. Entry expiration considers each entry on its own and > can expire one without the other. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/geode/pull/4022?email_source=notifications&email_token=AETOKID4VKPNRK7JYO3MEITQI7FUNA5CNFSM4IU6IVZ2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCEIHZHI#pullrequestreview-286293149>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AETOKIC563M323XQUY5DUSLQI7FUNANCNFSM4IU6IVZQ> > . > [ Full content available at: https://github.com/apache/geode/pull/4022 ] This message was relayed via gitbox.apache.org for [email protected]
