Hello! Do you have reproducer for that entity name issue? I would very much like to check that. Why do you need to add 'x' to it?
Regards, -- Ilya Kasnacheev чт, 28 янв. 2021 г. в 16:26, Maximiliano Gazquez <[email protected] >: > So we fixed it like this > > private static String fixEntityName(Function<String, Integer> > nameToTypeId, String name) { > String result = name; > while ((nameToTypeId.apply(result) & 0x000000FF) == 103) { > result = "x" + result; > } > return result; > } > Where nameToTypeId is BinaryBasicIdMapper#typeId basically and it works. > > Now, is there any way to calculate the ClientConfiguration size? To avoid > the issue mentioned in https://issues.apache.org/jira/browse/IGNITE-13401 > > A <https://issues.apache.org/jira/browse/IGNITE-13401>lso, we were using > thick client but we decided to migrate to thin client because we need > interoperability between version. Is there any documentation about this? > Detailing compatibility between client/server versions. > > Thanks! > On 28 Jan 2021 9:08 -0300, Pavel Tupitsyn <[email protected]>, wrote: > > Ilya, > > Normally you can use any combination of thin client and server versions, > the highest common protocol version is negotiated automatically > during the handshake. > > There are some exceptions to this - not all thin clients support very old > protocols, > but with recent versions it should work. > > On Thu, Jan 28, 2021 at 1:58 PM Ilya Kasnacheev <[email protected]> > wrote: > >> Hello! >> >> I don't think you can use a more recent version of thin client with older >> server version. >> New thin client features usually require support from the server side as >> well. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> ср, 27 янв. 2021 г. в 21:45, jjimeno <[email protected]>: >> >>> Hello, >>> >>> Thanks for your answer. >>> The server is already in version 2.9.1 and the c++ thin client is from >>> master branch to get transactions support. >>> >>> José >>> >>> >>> >>> -- >>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>> >>
