Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAGt6o8=A0O7qr1ZNPJXODOP792ff7ibw-CQSNZwttMyPVUHE_g@mail.gmail.com>
References: <CAGt6o8mcQwhqt1RsbRWJpXO5Xe5r1oMa=EXNHnqso=OMOh5cSQ@mail.gmail.com>
 <CA+eZwrH5L6SWWV_wim3thq0VYQm45WD_8QxMUrd=F1Un+m7tpg@mail.gmail.com>
 <CA+0=VoVeGmJW7h4jp360u5GS7qQ0oyMsh6YTOC2eTo_RyuCfiA@mail.gmail.com>
 <CA+eZwrFv6X12hMgwpAZqbZT8AvrCoG8m7pbhLh_JMephWKnvZw@mail.gmail.com>
 <CAK2_iMPO1+A457SxREabUb7COpXjbp1fhNAKM_jsQEQz4_cOSw@mail.gmail.com>
 <CA+eZwrFT7RXYAN-aQ1LkYHGsMDA14KjqFw_uu5uVaaxHKaHhaw@mail.gmail.com>
 <CA+0=VoWKCOkmH4za0Bo=5ZoraBV2iti2oGqWC1uCPjt0hWtAkg@mail.gmail.com>
 <CAK2_iMOk6V2wz14+P5KV-WjEuuncUGOPRTQoD3NqJ=KM2ZjZPA@mail.gmail.com>
 <CAK2_iMM8No=F0t51z8sOwCa4GcWfWbVapkqxCjN8gy2wSHvL+A@mail.gmail.com>
 <CA+eZwrEYapRKdkyYcZnHFCUuW-Dy5W4i4Ko4yB12_A0XwUK9Xg@mail.gmail.com> <CAGt6o8=A0O7qr1ZNPJXODOP792ff7ibw-CQSNZwttMyPVUHE_g@mail.gmail.com>
From: Sergi Vladykin <sergi.vladykin@gmail.com>
Date: Mon, 10 Apr 2017 20:43:16 +0300
Message-ID: <CA+eZwrG_5EAAyqz_Mes3h_fyWudc1E=yJKAT8x_uU-TONc7W6A@mail.gmail.com>
Subject: Re: Sorting fields of Binarilyzable objects on write
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a114d82f801f813054cd385f0
archived-at: Mon, 10 Apr 2017 17:44:08 -0000

--001a114d82f801f813054cd385f0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I'm sorry, looks like I do not really well understand this stuff, but it is
still not clear to me why wouldn't we just take the order of key fields
given in QueryEntity and use it for both cases irrespectively to the order
of fields in regular Class or in Binarylizable?

I mean lets say we have a Class (with unpredictable order of fields
according to reflection):

   Person implements Serializable
      {int age, double salary}

Or we have a Binarylizable (with some unknown user defined order of fields)=
:

  Person implements Binarylizable {
     writeBinary(w) {w.writeDouble("salary", salary),  w.writeInt(''age",
age)}

Also we have a QueryEntity (age, salary)

Why we can not take key fields names from QueryEntity in the given order
(age, salary) and get values from either "regular" Class or from
Binarylizable and calculate hash code?

Sergi

2017-04-10 19:56 GMT+03:00 Vladimir Ozerov <vozerov@gridgain.com>:

> Guys,
>
> The problem is that order of fields serialization is unknown for regular
> objects, where "regular" stands for non-Binarilyzable class. Reflection
> returns fields in unpredictable order. For this reason you cannot match
> fields order between class and QueryEntity. This is why we introduced
> sorting, and this is why idea to rely on QueryEntity doesn't work.
>
> On Mon, Apr 10, 2017 at 7:01 PM, Sergi Vladykin <sergi.vladykin@gmail.com=
>
> wrote:
>
> > Why "regular" are different here?
> >
> > Sergi
> >
> > 2017-04-10 18:59 GMT+03:00 Pavel Tupitsyn <ptupitsyn@gridgain.com>:
> >
> > > QueryEntity sorting is not an option for "regular" classes with
> > reflective
> > > serialization.
> > > We have to use alphabetical.
> > > Also, same class can participate in multiple query entities.
> > >
> > > 10 =D0=B0=D0=BF=D1=80. 2017 =D0=B3. 18:52 =D0=BF=D0=BE=D0=BB=D1=8C=D0=
=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Dmitriy Setrakyan" <
> > > dsetrakyan@apache.org> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
> > >
> > > On Mon, Apr 10, 2017 at 8:28 AM, Sergi Vladykin <
> > sergi.vladykin@gmail.com>
> > > wrote:
> > >
> > > > The decision to use alphabetic order looks strange here. Using orde=
r
> > > > provided in QueryEntity and require from user to have the same orde=
r
> > > > in Binarylizable
> > > > looks more reasonable.
> > > >
> > >
> > > I think this would be much harder to verify. Alphabetical order is mo=
re
> > > intuitive, no?
> > >
> >
>

--001a114d82f801f813054cd385f0--