[ https://issues.apache.org/jira/browse/NUTCH-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791411#action_12791411 ]
Andrzej Bialecki commented on NUTCH-775: ----------------------------------------- +1. I would suggest creating a subclass of Metadata, where we can guarantee the presence of some required parameters, e.g.: {code} public class SearchContext extends Metadata { protected int numHits; protected String sortField; protected String dedupField; ... // setters and getters for the above } {code} and change the QueryFilter interface to use SearchContext too. > Enhance Searcher interface > -------------------------- > > Key: NUTCH-775 > URL: https://issues.apache.org/jira/browse/NUTCH-775 > Project: Nutch > Issue Type: Improvement > Components: searcher > Reporter: Sami Siren > Assignee: Sami Siren > Fix For: 1.1 > > > Current Searcher interface is too limited for many purposes: > Hits search(Query query, int numHits, String dedupField, String sortField, > boolean reverse) throws IOException; > It would be nice that we had an interface that allowed adding different > features without changing the interface. I am proposing that we deprecate the > current search method and introduce something like: > Hits search(Query query, Metadata context) throws IOException; > Also at the same time we should enhance the QueryFilter interface to look > something like: > BooleanQuery filter(Query input, BooleanQuery translation, Metadata context) > throws QueryException; > I would like to hear your comments before proceeding with a patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.