DocValues or stored fields to enable atomic updates

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

DocValues or stored fields to enable atomic updates

ahubold
Hi,

I have a question on schema design: If a single-valued StrField is just
used for filtering results by exact value (indexed=true) and its value
isn't needed in the search result and not for sorting, faceting or
highlighting - should I use docValues=true or stored=true to enable
atomic updates? Or even both? I understand that either docValues or
stored fields are needed for atomic updates but which of the two would
perform better / consume less resources in this scenario?

Thank you.

Best regards,
Andreas



Reply | Threaded
Open this post in threaded view
|

Re: DocValues or stored fields to enable atomic updates

Emir Arnautović
Hi Andreas,
Stored values are compressed so should take less disk. I am thinking that doc values might perform better when it comes to executing atomic update.

HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/



> On 5 Apr 2019, at 12:54, Andreas Hubold <[hidden email]> wrote:
>
> Hi,
>
> I have a question on schema design: If a single-valued StrField is just used for filtering results by exact value (indexed=true) and its value isn't needed in the search result and not for sorting, faceting or highlighting - should I use docValues=true or stored=true to enable atomic updates? Or even both? I understand that either docValues or stored fields are needed for atomic updates but which of the two would perform better / consume less resources in this scenario?
>
> Thank you.
>
> Best regards,
> Andreas
>
>
>