: What would be the scope of the work to implement Erik's suggestion, I
: would have to ask my boss, but I think we would then contribute the code
: back to Solr.
The QParser modifications would be fairly straight forward -- adding some
setters to SolrQueryParser to set booleans telling when to
Hello all,
Sorry I have taken so long to get back to Eriks reply, I used the
technique of inserting a ? before the * to get at prototype working.
However, if 1.3 does not support this anymore, then I really need to
look into alternatives.
What would be the scope of the work to implement Erik's
Alas no, the queryparser now uses an unhighlightable constantscore
query. I'd personally like to make it work at the Lucene level, but not
sure how thats going to proceed. The tradeoff is that you won't have max
boolean clause issues and wildcard searches should be faster. It is a
bummer though
Hi,
I have another question on the wildcard problem:
In the previous Solr releases there was a workaround to highlight wildcard
queries using the StandardRequestHandler by adding a ? in between: e.g.
hou?* would highlight house.
But this is not working anymore. Is there maybe another workaround?
Probably your best bet is to create a new QParser(Plugin) that uses
Lucene's QueryParser directly. We probably should have that available
anyway in the core, just so folks coming from Lucene Java have the
same QueryParser.
Erik
On Sep 2, 2008, at 7:11 AM, Brian Carmalt wrote:
He
