I doubt it mattes. The only point for docValues is to speed up situations where you want to answer the question "for docX, what is the value of fieldY"? Unless you're doing something interesting with the_route_ field, it's only used to, well, route documents at index time. By "interesting", I'm talking grouping, faceting and sorting. Are you doing any of those things on the _route_ field? If not you might as well save the disk space by leaving docValues=false.
Best, Erick On Thu, Nov 22, 2018 at 7:44 AM Vincenzo D'Amore <v.dam...@gmail.com> wrote: > > Hi guys, this is an interesting thread. > > Looking at schema.xml I found having uniqueKey (type="string") configured > as docValues="true" but, I also found that _root_ is > configured docValues="false" > > Is there any drawbacks in having _root_ with docValues="false" ? > > > On Thu, Nov 22, 2018 at 12:28 AM Erick Erickson <erickerick...@gmail.com> > wrote: > > > In SolrCloud there are a couple of places where it might be useful. > > First pass each replica collects the top N ids for the aggregator to > > sort. If the uniqueKey isn't DV, it needs to either decompress it off > > disk or build an structure on heap if it's not DV. Last I knew anyway. > > > > Best, > > Erick > > On Wed, Nov 21, 2018 at 12:04 PM Walter Underwood <wun...@wunderwood.org> > > wrote: > > > > > > Is it a good idea to store the uniqueKey as docValues? A great idea? A > > maybe or maybe not idea? > > > > > > It looks like it will speed up export and streaming. Otherwise, I can’t > > find anything the docs pro or con. > > > > > > wunder > > > Walter Underwood > > > wun...@wunderwood.org > > > http://observer.wunderwood.org/ (my blog) > > > > > > > > -- > Vincenzo D'Amore
