AW: mergeContiguous for multiple search terms
Hallo, we are using Solr-1.3. Thanks for your time. Björn -Ursprüngliche Nachricht- Von: solr-user-return-24991-hachmann.bjoern=guj...@lucene.apache.or g [mailto:solr-user-return-24991-hachmann.bjoern=guj...@lucene.a pache.org] Im Auftrag von Avlesh Singh Gesendet: Montag, 10. August 2009 04:01 An: solr-user@lucene.apache.org Betreff: Re: mergeContiguous for multiple search terms Which Solr version are you using? Cheers Avlesh On Wed, Aug 5, 2009 at 5:55 PM, Hachmann, Bjoern hachmann.bjo...@guj.dewrote: Hello, we would like to use the highlightingComponent with the mergeContiguous parameter set to true. We have a field with value: Ökonom Charles Goodhart. If we search for all three words, they are found correctly: emÖkonom/em emCharles/em emGoodhart/em But, as I set the mergeContiguous parameter to true, I expected: emÖkonom Charles Goodhart/em. Am I misunderstanding the behaviour of this parameter? We are using the dismax-query parser and solr-1.3. Thank you very much for your time. Björn Hachmann
mergeContiguous for multiple search terms
Hello, we would like to use the highlightingComponent with the mergeContiguous parameter set to true. We have a field with value: Ökonom Charles Goodhart. If we search for all three words, they are found correctly: emÖkonom/em emCharles/em emGoodhart/em But, as I set the mergeContiguous parameter to true, I expected: emÖkonom Charles Goodhart/em. Am I misunderstanding the behaviour of this parameter? We are using the dismax-query parser and solr-1.3. Thank you very much for your time. Björn Hachmann
Cross-context-forward to solr-instance
Hi, yesterday I tried the Solr-1.3-RC2 and everything seems to work fine using the traditional single-core setup. But while troubleshooting the new multi-core feature, I realized for the first time, that I have been using the deprecated (even in 1.2) class SolrServlet. This is a huge problem for us, as we run the solr-web-app parallel to our main web-app in the same servlet-container. Using this approach we can internally forward update- and select-requests to the Solr-instance currently in use. ServletContext ctx = getServletContext().getContext(solr1); RequestDispatcher rd = ctx.getNamedDispatcher(SolrServer); rd.forward(request, response); As you can see, this approach only works for the servlet named 'SolrServer' which references the deprecated class. The attempt of using a path based dispatcher (ctx.getRequestDispatcher) was not successful, even though I configured the SolrRequestFilter in the solr-web.xml to work on forwards (dispatcherFORWARD/dispatcher), which the documentation discourages. Maybe this is because of the cross-context-dispatch? At the moment I ran totally out of ideas, apart from completely redesigning our whole setup. Any ideas are highly appreciated. Thanks in advance, Björn