bq: Keep a copy of the value into a non-multi-valued field, using an
update processor: This involves indexing a new field
Why can't you do this? You can't re-index the data perhaps? It's by
far the easiest solution
Best,
Erick
On Wed, May 20, 2015 at 2:45 AM, Fernando Agüero wrote:
> Hi ev
Hi everyone,
I’ve been reading answers around this problem but I wanted to make sure that
there is another way out of my problem. The thing is that the solution
shouldn’t be on index-time, involve indexing a new field or changing this
multi-valued field to a single-valued one.
Problem:
I need