Not finding any documentation about ordering, I thought I'd extend BasicQueryFilter to include my added query functionality. It seems this would be cleaner anyway.
But now I see something that looks like a bug in the plugin mechanism. In nutch-site.xml I configured query-basic to be ignored and my plugin to be included in the plugin.includes property, something like this (edited for clarity): <property> <name>plugin.includes</name> <value>...|query-(site|url)|query-myfilter|...</value> But because I extend the functionality of query-basic, it is a dependency for my plugin, so I include that in the my plugin.xml file: <requires> <import plugin="nutch-extensionpoints"/> <import plugin="query-basic"/> </requires> So what I think is the bug is that the query-basic filter is run anyway, independently of mine. So my filter runs, and I build clauses much like query-basic does, and after that, query-basic runs, adding its own clauses to the query. It seems to me that if query-basic is not in the plugin-includes property, it should not get invoked in the series of query filters. Is the behavior I'm observing really by design? Thx On 4/27/07, c wanek <[EMAIL PROTECTED]> wrote:
Is there a way I can configure a particular order to the Nutch query filters, and if so how? I would like to modify the query *after* the BasicQueryFilter has done its work. My filter was working this way with version 0.8, but now in 0.9, my filter seems to be getting invoked before BasicQueryFilter. I thought I saw something about this someplace in the docs, but now can't find it. Thanks Charlie
