[ 
https://issues.apache.org/jira/browse/SOLR-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254155#comment-15254155
 ] 

Joel Bernstein edited comment on SOLR-9027 at 4/22/16 4:16 PM:
---------------------------------------------------------------

Basic implementation. Tests still needed.

It doesn't do anything fancy to build up the matching docs. The main thing that 
it adds is the maxDocFreq param which is the threshold for discarding query 
terms.

This essentially creates an on-the-fly stop list for high frequency nodes that 
appear during a graph traversal.


was (Author: joel.bernstein):
Basic implementation. Test still needed.

It doesn't do anything fancy to build up the matching docs. The main thing that 
it adds is the maxDocFreq param which is the threshold for discarding query 
terms.

This essentially creates an on-the-fly stop list for high frequency nodes that 
appear during a graph traversal.

> 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
>
>
> 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]

Reply via email to