Hi, Thanks for reporting that issue and for the https://issues.apache.org/jira/browse/IGNITE-29191 ticket.
I'll have a look. On Fri, Oct 23, 2026 at 12:01 PM <[email protected]> wrote: > hi Reza > Thanks again for the quick response and verification! > > > > > Best regards, > > I.P. > > > ---------- Původní e‑mail ---------- > Od: Reza Taroosheh <[email protected]> > Komu: [email protected] > Kopie: [email protected] > Datum: 23. 10. 2026 9:53:35 > Předmět: Re: Local IndexQuery issue with binary object results in Ignite > 2.x > " > Hi I.P., > > Thanks for the report and the reproducer. I had actually noticed the same > behavior while working on the setLimit() fix, and I was still checking > what > changing it would affect before opening a ticket. Your reproducer confirms > it: a local IndexQuery returns binary objects even when the cache is not > in > keep-binary mode, while a distributed IndexQuery returns your own classes. > > I created a ticket for it: IGNITE-29199 > https://issues.apache.org/jira/browse/IGNITE-29199 > (https://issues.apache.org/jira/browse/IGNITE-29199) > > Until it's fixed, the workaround in your README could help: run the query > with "withKeepBinary()" and call "deserialize()" on each value. > > Best regards, > Reza > > > > On Fri, Oct 23, 2026 at 8:52 AM <[email protected](mailto:[email protected])> > > wrote: > > " > Hi devs > While analyzing and testing local IndexQuery features on Ingite 2.x it > looks > like that there might be another issue, which require your assistance > again. > It's about that a local IndexQuery returns binary objects on a cache that > is > not in keep-binary mode (verified on both 2.17 and 2.18 versions). > > > > > In the same manner as it was before I'm attaching a reproducer with a > detailed README.md file. > > > > > Could you please have a look and in case it's true provide a JIRA ticket > number? > > Many thanks in advance. > > > > > Best regards, > > I.P. > > " > " >
