Yeah, it is redundant, but I am using that to use the solr query response as input of a plugin function:
http://localhost:8983/solr/articles.0/select/?q={!func}myFunction(query({!query v='the query string here'})) So in myFunction I can take the query results, with the score, and write my custom sort/re-scorer. Is that the best way? On Thu, Jul 15, 2010 at 1:16 PM, Yonik Seeley <yo...@lucidimagination.com> wrote: > On Thu, Jul 15, 2010 at 11:51 AM, Rodrigo Rezende <rcreze...@gmail.com> wrote: >> I solved the problem. >> The correct syntax is: >> >> http://localhost:8983/solr/articles.0/select/?q={!func}query({!query >> v='hello'})&fl=Document.title,score,&debugQuery=on > > query() causes a new QParser to be created. so does {!query}... so > using both is redundant. > If you want an embedded lucene query, then you could do > > query({!lucene v='hello'}) > OR > query({!lucene v=$qq}) & qq=hello > OR, since lucene is the default query type > query($qq) & qq=hello > > -Yonik > http://www.lucidimagination.com >
