No, actually it's a .NET web service that queries Endeca (call it Wrapper). It returns to its clients a collection of unique product IDs, then the client will ask other web services for more detailed informations about the given products. As long as no URL redirection is involved, I think that solrnet ( http://code.google.com/p/solrnet/ ) is good enough to make our Wrapper connect to Solr, thus shielding the client from changes in the underlying search engine.
Endeca C# API also returns a 'RedirectionUrl' property in one of its object, which is set to an URL if the text search matches a redirection rule, in this case the Wrapper passes it down to its client (my fault here, I thought there was some sort of redirection through HTTP result code, but that's not the case). The point is: since Solr doesn't have this feature, my only chance is to implement it into the "wrapping" web service itself, but I need to "access" how the words are analyzed by the search engine to make it work correctly. AFAICS, Solr only returns documents matching the request, so I'm missing something :-( S ________________________________________ Inizio: Michael Kuhlmann [k...@solarier.de] Inviato: mercoledì 7 dicembre 2011 15.29 Fine: solr-user@lucene.apache.org Oggetto: Re: R: Solr response writer Am 07.12.2011 15:09, schrieb Finotti Simone: > I got your and Michael's point. Indeed, I'm not very skilled in web > devolpment so there may be something that I'm missing. Anyway, Endeca does > something like this: > > 1. accept a query > 2. does the stemming; > 3. check if the result of the step 2. matches one of the redirectable words. > If so, returns an URL, otherwise returns the regular matching documents (our > products' description). > > Do you think that in Solr I will be able to replicate this behaviour without > writing a custom plugin (request handler, response writer, etc)? Maybe I'm a > little dense, but I fail to see how it would be possible... Endeca not only is a search engine, it's part of a web application. You can send a query to the Endeca engine and send the response directly to the user; it's already fully rendered. (At least when you configured it this way.) Solr can't do this in any way. Solr responses are always pure technical data, not meant to be delivered to an end user. An exception to this is the VelocityResponseWriter which can fill a web template. Anything beyond the possibilities of the VelocityReponseWriter must be handled by some web application that anaylzes Solr's reponses. How do you want ot display your product descriptions, the default case? I don't think you want to show some XML data. Solr is a great search engine, but not more. It's just a small subset of commercial search frameworks like Endeca. Therefore, you can't simply replace it, you'll need some web application. However, you don't need a custom response writer in this case, nor do you have to Solr extend in any way. At least not for this requrement. -Kuli
