And if you want an opposite effect, you can ignore during Update Request
Processor pipeline.
Regards,
Alex
On Mon, Aug 6, 2018, 5:35 PM Shawn Heisey, wrote:
> On 8/6/2018 2:47 PM, John Davis wrote:
> > If a field is set as "ignored" (indexed=false, stored=false) can it be
> used
> > for an
On 8/6/2018 2:47 PM, John Davis wrote:
> If a field is set as "ignored" (indexed=false, stored=false) can it be used
> for another field as part of copyfield directive which might index/store it.
Yes.
The copyField directive is processed before the indexing process gets
the document. The origina
Hi John,
Yes it can and it is common pattern when you want to index multiple fields into
a single field or if you want to standardise naming without changing indexing
logic.
Thanks,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Trainin
Hi John,
Yes, it's possible.
Andrea
On Mon, 6 Aug 2018, 22:47 John Davis, wrote:
> Hi there,
> If a field is set as "ignored" (indexed=false, stored=false) can it be used
> for another field as part of copyfield directive which might index/store
> it.
>
> John
>
Hi there,
If a field is set as "ignored" (indexed=false, stored=false) can it be used
for another field as part of copyfield directive which might index/store it.
John
