Supplementing filter query with request filter query. about solrtexttagger HOT 3 CLOSED

Hi Justin. There is no forum or mailing list to my knowledge.

The earlier versions of the tagger request handler configured stuff at the top-level instead of following standard default/appends/invariants conventions. That still works but is deprecated; you should put all parameters in "defaults" or "invariants" as applicable. The solrconfig.xml you reference uses a mixed style; it really should be updated to minimize confusion. I think that if you put 'fq' in the defaults section, that the request will override it. If it doesn't work then it's a bug! I would like to keep setTopInitArgsAsInvariants private as it's likely to go away once we cut compatibility with the old style config, but it's not important.

But nonetheless the tagger only supports one 'fq' query, unlike a standard Solr search. It should be easy to add; "searcher.getDocSet(filterQuery)" takes a list of queries as well. Pull requests are welcome :-)

from solrtexttagger.

Thanks David! Using fq in "appends" along with handling multiple fq's in computeDocCorpus gives me what i need. I'll work on the pull request.

from solrtexttagger.

Hi Justin,

No mailing list currently.

The Xponents/Extraction/ geo pkg has a SolrGazetteer and a GazetteerMatcher that make use of the gazetteer core directly. SolrGaz facilitates the most common search routines, while GazMatcher is the SolrTextTagger implementation where the "/tag" request processor comes into play. So, GazMatcher is the class I'd target for adding this live feature -- adapting the solr params to /tag, such as extending the "fq" or other params.

I'm working on Xponents v2.7d SNAPSHOT -- in master; Currently running through testing that... Once 2.7.1 is finally released (after going through a,b,c,d fix up releases), I'll start managing changes off in branches. Overdue for a documentation release, too.

thanks for the feedback.

Marc

from solrtexttagger.