[ https://issues.apache.org/jira/browse/LUCENE-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724061#comment-16724061 ]
Alan Woodward commented on LUCENE-8613: --------------------------------------- If you're happy treating multi-valued fields as a set, then you can write a LongValuesSource implementation that counts the number of values in the set when advanceExact() is called - having a look at how LongValuesSource.FieldValuesSource works should give you a good start. > CoveringQuery to use multi-valued field length as minimum match > --------------------------------------------------------------- > > Key: LUCENE-8613 > URL: https://issues.apache.org/jira/browse/LUCENE-8613 > Project: Lucene - Core > Issue Type: Improvement > Affects Versions: 7.5 > Reporter: Tristan Stevens > Priority: Minor > > Currently CoveringQuery uses a long field's value for the minimumMatch for > each document. > There are use cases where this value may be derived from the length of a > multi-valued field (including docValues). > This request is to support an alternative constructor and implementation for > CoveringQuery to take a field name that can be used for the per-document > minimum match value. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org