Re: Search combination?

I assume you are using the StandardRequestHandler, so this should work: http://192.168.105.54:8983/solr/itas?q=size:7* AND extension:pdf Also have a look at the follwing links: http://wiki.apache.org/solr/SolrQuerySyntax http://lucene.apache.org/java/2_4_1/queryparsersyntax.html Thomas Jörg

Re: grouping response docs together

Hello Matt, the patch should work with trunk and after a small fix with 1.3 too (see my comment in SOLR-236). I just made a successful build to be sure. Do you see any error messages? Thomas Matt Mitchell schrieb: Thanks guys. I looked at the dedup stuff, but the documents I'm adding aren't

Re: Sorting TEXT Field problems :-(

Kraus, Ralf | pixelhouse GmbH schrieb: Hello, Querry: {wt=jsonrows=30json.nl=mapstart=0sort=RezeptName+asc} Result : Doppeldecker Eiersalat Curry - Eiersalat Eiersalat Why is my second Curry... after Doppeldecker ??? RezeptName is a normal text field defined as : fieldType name=text

Re: AW: Converting German special characters / umlaute

Hostetter noted, stored fields always return the initial value, which turned the second part of my question obsolete. Thanks a lot for your help! best Matthias -Ursprüngliche Nachricht- Von: Thomas Traeger [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 26. September 2007 23:44

Re: Different search results for (german) singular/plural searches - looking for a solution

Martin Grotzke schrieb: Try the SnowballPorterFilterFactory with German2 as language attribute first and use synonyms for combined words i.e. Herrenhose = Herren, Hose. so you use a combined approach? Yes, we define the relevant parts of compounded words (keywords only) as synonyms

Re: Different search results for (german) singular/plural searches - looking for a solution

in short: use stemming Try the SnowballPorterFilterFactory with German2 as language attribute first and use synonyms for combined words i.e. Herrenhose = Herren, Hose. By using stemming you will maybe have some interesting results, but it is much better living with them than having no or

Re: Converting German special characters / umlaute

Try the SnowballPorterFilterFactory described here: http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters You should use the German2 variant that converts ä and ae to a, ö and oe to o and so on. More details: http://snowball.tartarus.org/algorithms/german2/stemmer.html Every document in

Re: All facet.fields for a given facet.query?

: Faceting on manufacturers and categories first and than present the : corresponding facets might be used under some circumstances, but in my case : the category structure is quite deep, detailed and complex. So when : the user enters a query I like to say to him Look, here are the :

Re: All facet.fields for a given facet.query?

Martin Grotzke schrieb: On Tue, 2007-06-19 at 19:16 +0200, Thomas Traeger wrote: Hi, I'm also just at that point where I think I need a wildcard facet.field parameter (or someone points out another solution for my problem...). Here is my situation: I have many products of different

Re: All facet.fields for a given facet.query?

Chris Hostetter schrieb: : to make it clear, i agree that it doesn't make sense faceting on all : available fields, I only want faceting on those 300 attributes that are : stored together with the fields for full text searches. A : product/document has typically only 5-10 attributes. : : I like

Re: All facet.fields for a given facet.query?

Hi, I'm also just at that point where I think I need a wildcard facet.field parameter (or someone points out another solution for my problem...). Here is my situation: I have many products of different types with totally different attributes. There are currently more than 300 attributes