OK so it means it follows same contract as per java hashcode equals where
in case hashcode and equality stays it will always refer to same object
when newly created provided their pdx serializaion binary remains same.
I asked as I am going to store complex object graph which internally may
refer same instruments within same region.
Please correct me or guide me if there is anything else as well I should
take care of.
Thanks,
Dharam
On 4 Aug 2016 23:17, "Michael Stolz" <mst...@pivotal.io> wrote:
> If the referenced instruments have the same key they will just behave as
> updates to the same entry. You will not get duplicates.
>
> --
> Mike Stolz
> Principal Engineer, GemFire Product Manager
> Mobile: 631-835-4771
>
> On Thu, Aug 4, 2016 at 6:53 AM, Dharam Thacker <dharamthacke...@gmail.com>
> wrote:
>
>> Hi All,
>>
>> I am bit new to this.
>>
>> Could some one help me to understand region storage? I have following
>> Instrument instance which internally refers to many Instrument instances
>> via Basket.
>>
>> There is 1 Instrument region which contains all instruments. Would there
>> be duplicate instrument objects created within Basket even though similar
>> Instrument object exists within region (By hashcode/equals - Reference
>> point of view)
>>
>> Class Instrument{
>> Basket backet;h
>> }
>>
>> Class Backet{
>> List<Constituent> constituents;
>> }
>>
>> Class Constituent {
>> List<Instrument> instruments;
>> }
>>
>>
>> Thanks,
>> - Dharam Thacker
>>
>
>
