entException {
checkConnectedAndExists(areaName);
Query> sql = new ScanQuery<>(new
Predicate<>());
try (QueryCursor> cursor =
ignite.cache(areaName).withKeepBinary().query(sql)) {
return returnEntry(cursor);
Hi Ilya,
I tested it with nightly build of 17/09/2018(ver.
2.7.0.20180917#19700101-sha1:DEV), but getting the same exception. Getting
the following exception while trying to fetch the data from cache using
ScanQuery from Java Thin client, but SqlQuery giving the correct result.
ScanQuery
)
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:698)
... 23 more
Thanks
Saby
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ScanQuery is reporting the following exception while trying to fetch the data
from remote Ignite Server through the Java thing client keeping the
peerClassLoading is enabled, But SqlQuery is fetching the correct result and
is sending it back to the client.
If Lamda expression is used as filter in
