dsmiley commented on a change in pull request #1151: SOLR-13890: Add 
"top-level" DVTQ implementation
URL: https://github.com/apache/lucene-solr/pull/1151#discussion_r365345185
 
 

 ##########
 File path: solr/solr-ref-guide/src/other-parsers.adoc
 ##########
 @@ -1037,11 +1037,11 @@ An optional parameter used to determine which of 
several query implementations s
 +
 `termsFilter` the default `method`.  Uses a `BooleanQuery` or a 
`TermInSetQuery` depending on the number of terms.  Scales well with index 
size, but only moderately with the number of query terms.
 +
-`docValuesTermsFilter` can only be used on fields with docValues data.  
Chooses between the `docValuesTermsFilterTopLevel` and 
`docValuesTermsFilterPerSegment` methods using the number of query terms as a 
rough heuristic.  Users should typically use this method instead of using 
`docValuesTermsFilterTopLevel` or `docValuesTermsFilterPerSegment` directly, 
unless they've done performance testing to validate one of the methods on 
queries of all sizes.  Depending on the implementation picked, this method may 
rely on expensive data structures which are lazily populated after each commit. 
 If you commit frequently and your use-case can tolerate a static warming 
query, consider adding one to `solrconfig.xml` so that this work is done as a 
part of the commit itself and not attached directly to user requests.
+`docValuesTermsFilter` can only be used on fields with docValues data.  The 
`cache` parameter is false by default.  Chooses between the 
`docValuesTermsFilterTopLevel` and `docValuesTermsFilterPerSegment` methods 
using the number of query terms as a rough heuristic.  Users should typically 
use this method instead of using `docValuesTermsFilterTopLevel` or 
`docValuesTermsFilterPerSegment` directly, unless they've done performance 
testing to validate one of the methods on queries of all sizes.  Depending on 
the implementation picked, this method may rely on expensive data structures 
which are lazily populated after each commit.  If you commit frequently and 
your use-case can tolerate a static warming query, consider adding one to 
`solrconfig.xml` so that this work is done as a part of the commit itself and 
not attached directly to user requests.
 
 Review comment:
   Just a side-comment about our ref docs:  In the ref docs I write or update, 
I convert them to one sentence per line.  This makes the diffs easy to read!  
The pain of no newlines is very apparent here.  Change or not as you wish.  CC 
@ctargett 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to