ursday, October 12, 2017 5:53 PM
To: user@ignite.apache.org
Subject: Re: Indexing fields of non-POJO cache values
Just as idea.
What if we can to declare a kind of "references" or "aliases" for fields in
such cases?
And this will help us to avoid duplication of data.
For ex
-
> *From:* Andrey Mashenkov <andrey.mashen...@gmail.com>
> *Sent:* Thursday, October 12, 2017 6:25 AM
> *To:* user@ignite.apache.org
> *Subject:* Re: Indexing fields of non-POJO cache values
>
> Hi,
>
> Another way here is to implement your own query engine by e
supported BinaryObject field/POJO attribute.
Regards
Andrey
From: Andrey Mashenkov <andrey.mashen...@gmail.com>
Sent: Thursday, October 12, 2017 6:25 AM
To: user@ignite.apache.org
Subject: Re: Indexing fields of non-POJO cache values
Hi,
Another wa
Hi,
There is no way to index such data as is. To index data you need to have
entry_field<->column mapping configured.
As a workaround here, leaves can be stored in cache as values.
E.g. you can have a separate cache to index leaf nodes, where entries will
have 2 fields: "original tree key" field
Hello,
Consider the following use case: my cache values are a serialized tree-like
structure (as opposed to a POJO). The leaf nodes of the tree are Java
primitives. Some of the leaf nodes are used by the queries and should be
indexed.
What are my options for indexing such data?
Thanks
Andrey
