I think the answer is yes, that there's a better way to doing all of this. But
I'm not yet sure what this all entails in your situation. What are you
overriding with the Lucene searches? I imagine Solr has the flexibility to
handle what you're trying to do without overriding anything core in
SolrIndexSearcher.
Generally, the way to get a custom filter in place is to create a custom query
parser and use that for your fq parameter, like fq={!myparser param1='some
value'}possible+expression+if+needed, so maybe that helps?
Tell us more about what you're doing specifically, and maybe we can guide you
to a more elegant way to plug in any custom logic you want.
Erik
On Dec 26, 2012, at 11:21 , Nalini Kartha wrote:
> Hi,
>
> I'm trying to figure out how to convert the fq params that are being passed
> to Solr into something that can be used to filter the results of a query
> that's being issued against the Lucene IndexSearcher (I'm modifying some
> Lucene code to issue the query so calling through to one of the
> SolrIndexSearcher methods would be ugly).
>
> Looks like one of the IndexSearcher.search(Query query, Filter filter, ...)
> methods would do what I want but I'm wondering if there's any easy way of
> converting the fq params into a Filter? Or is there a better way of doing
> all of this?
>
> Thanks,
> Nalini
