Re: Sorting result of ScanQuery

Hello! It sounds like you need some data normalization plus SQL secondary indexes. Regards, -- Ilya Kasnacheev чт, 3 июн. 2021 г. в 17:11, Taner Ilyazov : > That's my concern. Because the requirements I have is persisting an Object > with a complex nested structure, which can't be changed. I

Re: Sorting result of ScanQuery

That's my concern. Because the requirements I have is persisting an Object with a complex nested structure, which can't be changed. I mean the class files can not be changed. Creating Data transfer objects and mapping between them is fine. But what we want to achieve is a really high write rate and

Re: Sorting result of ScanQuery

You can store collections in Ignite, the challenge is they’re effectively invisible to SQL. In general it’s easiest to work with data in relational structure. Ignite isn’t a document database. > On 3 Jun 2021, at 12:52, Taner Ilyazov wrote: > > Okay, but since the nested object structure that

Re: Sorting result of ScanQuery

Okay, but since the nested object structure that I have contains a Map, for which the idea is to have dynamic values, I'm not sure how it will be handled. Do I need to create a separate table to do the mapping of said Map<>? Couldn't find an example mapping a query entity entry to a parameterized v

Re: Sorting result of ScanQuery

A scan isn’t ordered. As you suspect, the way to order queries in Ignite is to use SQL. You don’t need to use annotations to define your SQL fields, indexes, etc. A slightly more verbose way is to use Query Entities (indexes

Sorting result of ScanQuery

Hello everyone, I'm new to the community and fairly new to Apache Ignite. I have a question for which I couldn't find a confirmation if it's possible or not. I have a use case where I need to persist a certain POJO to an ignite cluster. The POJO can not be changed, so adding @SqlQueryField to it'