> I believe it has something to do with backward compatibility.That's what I
> would like to know.If there's no strong reason to set it to false, it should
> be as Ignite's default -- that's what a user would expect. And if the user
> changes the configuration at the cluster, he/she will be aware of that and
> change it at thin client.If we cannot set it to Ignite's default, we can add
> a log message saying we force it to false.
--
Roman
On Thursday, January 17, 2019, 7:11:05 p.m. GMT+9, Igor Sapego
<isap...@apache.org> wrote:
First of all, I do not like that thin client is silently returns null. It
should be fixed.
For the compact footer being set to false by default - I believe it has
something to do withbackward compatibility.
Best Regards,Igor
On Thu, Jan 17, 2019 at 7:37 AM Roman Shtykh <rsht...@yahoo.com.invalid> wrote:
Igniters,
After putting some data with a user-defined key with a thick client, it's
impossible to retrieve it with a thin
client.https://issues.apache.org/jira/browse/IGNITE-10960(I was not sure it was
a bug, so I first reported the issue to the user ml, Mikhail thanks for
checking and the jira issue)
That happens because for Ignite `compactFooter` is `true` by default, but
`ClientBinaryMarshaller` forces it to `false` if `BinaryConfiguration` is not
created explicitly (see ClientBinaryMarshaller#createImpl).
Any reason to force it to false? I would like to align it with Ignite defaults
(by setting to true).
-- Roman
