[
https://issues.apache.org/jira/browse/SOLR-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264109#comment-15264109
]
David Smiley commented on SOLR-9027:
------------------------------------
Nice [~joel.bernstein].
BTW about collectTermContext, to be more clear on what I said earlier, which
may have been overlooked -- we're calling fields.terms(term.field()) on every
single term given. But they will all be the same as this is used for just one
field. Even if we wanted to support multiple fields, this terms variable could
be declared outside the loop and then only re-fetch if the current field for
this loop iteration is different than that of the previous. Granted I don't
know if a lot of terms is normal or the rare case for GraphTermsQuery but I
suspect a lot. This is another reason for the sort I advocated for.
> Add GraphTermsQuery to limit traversal on high frequency nodes
> --------------------------------------------------------------
>
> Key: SOLR-9027
> URL: https://issues.apache.org/jira/browse/SOLR-9027
> Project: Solr
> Issue Type: New Feature
> Reporter: Joel Bernstein
> Priority: Minor
> Attachments: SOLR-9027.patch, SOLR-9027.patch, SOLR-9027.patch,
> SOLR-9027.patch
>
>
> The gatherNodes() Streaming Expression is currently using a basic disjunction
> query to perform the traversals. This ticket is to create a specific
> GraphTermsQuery for performing the traversals.
> The GraphTermsQuery will be based off of the TermsQuery, but will also
> include an option for a docFreq cutoff. Terms that are above the docFreq
> cutoff will not be included in the query. This will help users do a more
> precise and efficient traversal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
