-
Bug
-
Resolution: Done
-
Major
-
None
-
None
There are two issues when trying to iterate caches configured with compatibility:
1) Since the client-side key tracker calculates segments based on byte[] keys, and the routing on the server is done via Object, there's a mismatch between segments calculated in the server and the client casing NPEs that prevent the data from the socket to be consumed correctly, resulting sometimes in:
org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid magic number. Expected 0xa1 and received 0x0 at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:313) at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:115) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) at org.infinispan.client.hotrod.impl.operations.IterationEndOperation.execute(IterationEndOperation.java:34) at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.close(RemoteCloseableIterator.java:64)
2) When the cache configuration has a different name than the cache, CCE errors are thrown:
org.infinispan.client.hotrod.exceptions.HotRodClientException: java.lang.ClassCastException: java.lang.Integer cannot be cast to [B at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343) ~[infinispan-client-hotrod-9.0.0-SNAPSHOT.jar:9.0.0-SNAPSHOT]
- causes
-
ISPN-6543 Spark connector fails with CCE when compatibility mode is enabled
- Closed