> This is definitely an interesting case that i don't think anyone ever > really considered before. It seems like a strong argument in favor of > adding an "hl.q" param that the HighlightingComponent would use as an > override for whatever the QueryComponent thinks the highlighting query > should be, that way people expressing complex queries like you you > describe could do something like... > > qq=solr > q=inStock:true AND+_query_:"{!dismax v=$qq}" > hl.q={!v=$qq} > hl=true > fl=name > hl.fl=name > bq=server > > ...what do you think? > > wanna file a Jira requesting this as a feature? Pretty sure the change > would only require a few lines of code (but of course we'd also need JUnit > tests which would probably be several dozen lines of code)
First of all, thanks for answering both of my LocalParams-related queries back in September. I somehow failed to notice your responses until today - it's alarmingly easy to lose things in the flood of solr-user mail - but I greatly appreciate your input on both issues! It looks like there's already a JIRA ticket (more than a year old) for the hl.q param: https://issues.apache.org/jira/browse/SOLR-1926 This definitely sounds like it would solve my problem, so I've put in my vote! - Demian