I don't think it is appropriate to store objects of 2GB size in Geode. I know we have hit networking issues with such large objects in the past.
-- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771 On Sun, Jul 9, 2017 at 2:13 AM, Daniel Farcovich < daniel.farcov...@amdocs.com> wrote: > Raising this question again. > > Daniel > > From: Daniel Farcovich > Sent: Wednesday, July 05, 2017 1:26 PM > To: 'dev@geode.apache.org' <dev@geode.apache.org> > Subject: getSizeInBytes() return type > > > Hi, > We implement getSizeInBytes() in from Sizeable interface. > We have objects with size bigger than MAXINT, bigger than 2GB. > What is the impact of refactoring the code to return long instead of int? > I mean except the technical aspect of changing the return types of the > calling functions etc. > Which mechanisms / functionalities will be affected from this change, I > know rebalancing will be affected for example. > > Thanks, > Daniel Farcovich > > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer < > https://www.amdocs.com/about/email-disclaimer> >
