Gal, I sent you a PM. I don’t think the Geode community can help with this question.
Anthony > On Jan 29, 2017, at 4:58 AM, Gal Palmery <gal.palm...@amdocs.com> wrote: > > I'll edit the mail a bit (it was in a table when I sent it, but I see that > it's not very clear) --> > > Can anyone say if the fixes for the below Gemfire support tickets are > included in the last geode release: > 1) 15611661002 - FIXED in GemFire 8.0.0.10 - gfsh fails to connect to locator > when executng a pre-configuration script, but returns 0 > 2) 15674334505 - fixed in GemFire 8.2 - NPE in map index when field of type > Map == null > 3) 16972460504 - FIXED in GemFire 8.2.0.1 - Gemfire server disconnected after > large GC pause > 4) 16972415504 - FIXED in GemFire 8.2.0.7 - Different results in OQL queries > for the same entity (using GFSH): one query is for all entities in a region, > and the second is for the specific entity. > > Thanks, > Gal > -----Original Message----- > From: Gal Palmery > Sent: Thursday, January 26, 2017 16:07 > To: dev@geode.apache.org > Subject: are these gemfire bug fixes included in the last geode release? > > Hi All, > > Can anyone say if the fixes for the below Gemfire support tickets are > included in the last geode release: > > Support ticket > > Issue > > Status > > Comment > > 15611661002 > > gfsh fails to connect to locator when executng a pre-configuration script, > but returns 0 > > FIXED > > FIXED in GemFire 8.0.0.10 > > 15674334505 > > NPE in map index when field of type Map == null > > FIXED > > fixed in GemFire 8.2 > > 16972460504 > > Gemfire server disconnected after large GC pause > > FIXED > > FIXED in GemFire 8.2.0.1 > > 16972415504 > > Different results in OQL queries for the same entity (using GFSH): one query > is for all entities in a region, and the second is for the specific entity. > > FIXED > > FIXED in GemFire 8.2.0.7 > > > Thanks, > Gal > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at http://www.amdocs.com/email_disclaimer.asp > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at http://www.amdocs.com/email_disclaimer.asp >
