You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by tschauenberg <ts...@invidi.com> on 2020/01/30 21:07:13 UTC

Re: CompactFooter for ClientBinaryMarshaller

Igor, can you have a look at
https://issues.apache.org/jira/browse/IGNITE-12003 and link it to
https://issues.apache.org/jira/browse/IGNITE-10960?

Using Java 2.7.0 thin client, Java 2.7.0 thick client and Java 2.7.0 Ignite
servers I first hit IGNITE-10960 and then reading your comments and the
proposed fix and this mailing list I tried to set the compact header in the
thin client to true to match the thick client but then hit the bug from
IGNITE-12003.

We hope to upgrade to 2.7.6 as soon but until we do I can't confirm the
behaviour is still a problem in 2.7.6.  I suspect it still is given
IGNITE-12003 reports the bug in 2.7.5.  



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: CompactFooter for ClientBinaryMarshaller

Posted by Ivan Pavlukhin <vo...@gmail.com>.
Both issues are related to "compact footer".

https://issues.apache.org/jira/browse/IGNITE-10960 is about comparison
equal objects with and without compact footer.
https://issues.apache.org/jira/browse/IGNITE-12003 is about binary
metadata retrieval by thin client for objects with compact footer.

I suppose both problems are present in 2.7.6 (and even in upcoming
2.8). The safest workaround so far is using compactFooter=false
everywhere.

Feel free to contribute a patch fixing any of the problems. Do not
hesitate to ask if you need any assistance.

пт, 31 янв. 2020 г. в 00:07, tschauenberg <ts...@invidi.com>:
>
> Igor, can you have a look at
> https://issues.apache.org/jira/browse/IGNITE-12003 and link it to
> https://issues.apache.org/jira/browse/IGNITE-10960?
>
> Using Java 2.7.0 thin client, Java 2.7.0 thick client and Java 2.7.0 Ignite
> servers I first hit IGNITE-10960 and then reading your comments and the
> proposed fix and this mailing list I tried to set the compact header in the
> thin client to true to match the thick client but then hit the bug from
> IGNITE-12003.
>
> We hope to upgrade to 2.7.6 as soon but until we do I can't confirm the
> behaviour is still a problem in 2.7.6.  I suspect it still is given
> IGNITE-12003 reports the bug in 2.7.5.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/



-- 
Best regards,
Ivan Pavlukhin