Hi, Another way here is to implement your own query engine by extending IndexingSPI interface, which looks much more complicated.
On Thu, Oct 12, 2017 at 4:23 PM, Andrey Mashenkov < [email protected]> wrote: > 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 and "leaf node value" indexed > field. > So, you will be able to query serialized tree-like structures via SQL > query with JOIN condition on "original tree key" and WHERE condition on > "leaf node value" field. > Obviously, you will need to implement intermediate logic to keep data of > both caches consistent. > > > On Wed, Oct 11, 2017 at 9:40 PM, Andrey Kornev <[email protected]> > wrote: > >> 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 >> > > > > -- > Best regards, > Andrey V. Mashenkov > -- Best regards, Andrey V. Mashenkov
