Thanks a lot for the reply.
I thought, might be a good idea to sort of override operator names, same
like stop words, stems, etc. I guess I'd need to parse the query string?
As for keeping state between requests, there's always going to be some
state going in order to have a drill-down session on facets. All
interesting state properties are actually in the Solr reponse, e.g.
queries, facets, start row, etc. Would save me some Javascript if the
facet URL was there as well... (no big fan of javascript...)
Shalin Shekhar Mangar a écrit :
On Sat, Aug 16, 2008 at 10:20 PM, Pierre Auslaender <[EMAIL PROTECTED]>wrote:
1/ Is it possible to localise query operator names without writing code?
For instance, I'd like to issue queries with French operator names, e.g. ET
(instead of AND), OU (instead of OR), etc.
No, your application must do it before sending the query to Solr.
2/ Is it possible for Solr to generate, in the XML response, the URLs or
complete queries for each facet in a faceted search?
It's not too difficult, but surely Solr could add this URL or query string
under the "material" element. Is this possible? Or do I have to XSLT the
result myself?
No, Solr does not do that. However generating them from Solr is a good idea
only if you are able to keep the state across requests.
