On Mon, Oct 16, 2017 at 12:35 PM, Andrey Kornev <andrewkor...@hotmail.com> wrote:
> [Crossposting to the dev list] > > Alexey, > > Yes, something like that, where the "reference"/"alias" is expressed as a > piece of Java code (as part of QueryEntity definition, perhaps) that is > invoked by Ignite at the cache entry indexing time. > > My point is that rather than limiting indexable fields only to predefined > POJO attributes (or BinaryObject fields) Ignite could adopt a more general > approach by allowing users designate an arbitrary piece of code (a > lambda/closure) to be used as an index value extractor. In such case, the > current functionality (extracting index values from POJO attributes) > becomes just a special case that's supported by Ignite out of the box. > Andrey, this would require deserialization on the server side. It would also require that user classes are present on the server side. Both of this scenarios Ignite tries to avoid. Makes sense?
