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'
etc.
> A slightly more verbose way is to use Query Entities (indexes
> <https://ignite.apache.org/docs/latest/SQL/indexes#configuring-indexes-using-query-entities>
> ).
>
> On 26 May 2021, at 14:24, Taner Ilyazov wrote:
>
> Hello everyone,
>
> I'm new to the co
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 I have conta
Hello everyone, I'm trying to find a solution for the current case:
I have generated classes, which can't be changed.
public static class CacheName {
private Long id;
private NestedClass nestedClass;
}
public static class NestedClass {
private List types;
private Map dynamicField
can't filter or order based on those properties.
On Fri, 4 Jun 2021 at 09:54, Taner Ilyazov wrote:
> Hello everyone, I'm trying
ould just be a
> join/filter against the CacheNameType table.
>
> You could do that as you feed the data in. You could do it using something
> like a ContinuousQuery to update the child tables dynamically.
>
> On 4 Jun 2021, at 08:05, Taner Ilyazov wrote:
>
> We need to be
