There appears to be consensus that this is a critical fix. The following commit has been brought into release/1.12 as the critical fix for GEODE-7763:
git cherry-pick -x b4c3e9413f0008635b0a0c9116c96147d1e4ceec GEODE-7763 has been marked as 'resolved in' 1.12. Regards EB On Wed, Mar 18, 2020 at 12:56 PM Donal Evans <doev...@pivotal.io> wrote: > +1 > > On Wed, Mar 18, 2020 at 12:32 PM John Blum <jb...@pivotal.io> wrote: > > > +1 > > > > On Wed, Mar 18, 2020 at 11:52 AM Owen Nichols <onich...@pivotal.io> > wrote: > > > > > +1 > > > > > > > On Mar 18, 2020, at 11:49 AM, Dick Cavender <dcaven...@pivotal.io> > > > wrote: > > > > > > > > +1 > > > > > > > > On Wed, Mar 18, 2020 at 11:43 AM Nabarun Nag <n...@apache.org> > wrote: > > > > > > > >> +1 > > > >> > > > >> On Wed, Mar 18, 2020 at 11:41 AM Jason Huynh <jhu...@pivotal.io> > > wrote: > > > >> > > > >>> Hello Dev list, > > > >>> > > > >>> I'd like to include a fix for GEODE-7763 in release 1.12.0. > > > >>> The change removes the call to exportValue, preventing a > > serialization, > > > >>> when no clients are waiting for the specific event. > > > >>> The reason why I think it should be in the release is that we > > noticed a > > > >>> negative effect on performance for a specific use case, in 1.12 > from > > a > > > >>> change that made us more "consistent" in that use case. This > change > > > >>> doesn't modify the fix much, but does bring performance back inline > > (if > > > >> not > > > >>> better) than before. > > > >>> > > > >>> The sha is b4c3e9413f0008635b0a0c9116c96147d1e4ceec > > > >>> > > > >>> Thanks, > > > >>> -Jason > > > >>> > > > >> > > > > > > > > > > -- > > -John > > Spring Data Team > > >
