Hello fellow devs,
I just wanted to ask, how would this Binary Object format change affect
thin clients? C++/.Net nodes? Etc?
Is it fully backwards compatible or not?
I think that realistically, we can only add binary-incompatible changes to
Binary Object format in 3.0.
Regards,
--
Ilya Kasnac
Hi!
Ilya, unfortunatelly yes, subsequent changes should be made in C++, .NET
and other platform code.
ср, 8 июл. 2020 г. в 12:22, Ilya Kasnacheev :
> Hello fellow devs,
>
> I just wanted to ask, how would this Binary Object format change affect
> thin clients? C++/.Net nodes? Etc?
>
> Is it fully
Denis Garus created IGNITE-13228:
Summary: Remote filter of IgniteEvents has to run with appropriate
SecurityContext.
Key: IGNITE-13228
URL: https://issues.apache.org/jira/browse/IGNITE-13228
Project:
Hello!
I think this is a blocker for this change. We already have binary format
published:
https://apacheignite.readme.io/docs/binary-client-protocol-data-format#complex-object
Arguably, we cannot change it in a minor version of Apache Ignite, so this
change has to target AI 3.0.
Extending this
I think that this feature can be handled as compactFooter. For example, C++
doesn't support compactFooter and it is not an issue.
Of course, this feature should be disabled by default, and should be
enabled explicitly in BinaryConfiguration.
Also, subsequent issues in jira about this feature suppor
Hello!
Yes, I think this is a sensible approach.
Regards,
--
Ilya Kasnacheev
ср, 8 июл. 2020 г. в 14:46, Ivan Daschinsky :
> I think that this feature can be handled as compactFooter. For example, C++
> doesn't support compactFooter and it is not an issue.
> Of course, this feature should be
Stanilovsky Evgeny created IGNITE-13229:
---
Summary: GridClient instance leakage.
Key: IGNITE-13229
URL: https://issues.apache.org/jira/browse/IGNITE-13229
Project: Ignite
Issue Type: Imp
