DocValues are irrelevant for scoring. Here’s the way I think of it. When querying (and thus scoring), you have a term X. I need to know > what docs does it appear in? > how many docs does it appear in? > how often does the term appear in the entire corpus?
These are questions the inverted index (indexed=“true”) was designed to answer. For faceting, sorting and grouping, I want to know for a _document_, what value appears in field Y. This is what docValues does much more efficiently. Best, Erick > On Jul 8, 2019, at 5:36 PM, Ashwin Ramesh <ash...@canva.com> wrote: > > Hi everybody, > > I can't find concrete evidence whether docValues are indeed useful for > filter queries. One example of a field: > > <field name="docHash" type="integer" indexed="true" stored="false" > required="false" multiValued="false" /> > > This field will have a value between 0-10000 The only usecase for this > field is to filter on a range / subset of values. There will be no scoring > / querying on this field. Is this a good usecase for docValues? Regards, Ash > > -- > *P.S. We've launched a new blog to share the latest ideas and case studies > from our team. Check it out here: product.canva.com > <https://product.canva.com/>. *** > ** <https://www.canva.com/>Empowering the > world to design > Also, we're hiring. Apply here! > <https://about.canva.com/careers/> > <https://twitter.com/canva> > <https://facebook.com/canva> <https://au.linkedin.com/company/canva> > <https://twitter.com/canva> <https://facebook.com/canva> > <https://au.linkedin.com/company/canva> <https://instagram.com/canva> > > > > > >
