Possible to adjust FieldNorm?

Hi, Is it possible to adjust FieldNorm? I have a scenario where the search is not producing the desired result because of fieldNorm: Search terms: coaching leadership Record 1: name="Ask the Coach", desc="...",... Record 2: name="Coaching as a Leadership Development Tool Part 1", desc="...",...

Re: Possible to adjust FieldNorm?

Sorry, I did not give the full output in the first post. For what it looks, the fieldNorm is saying that: 1 match out of 3 words in record 1 is more significant than 2 matches out of 8 words in record 2. That would be true for simple arithmetic, but unsatisfactory in human 'meaning'. Here are the

Facet filter: how to specify OR expression?

Hi, Is there anyway to specify an 'OR' expression for facet filter? For example docType="pdf" or docType="txt" Many thanks in advance. Yee -- View this message in context: http://lucene.472066.n3.nabble.com/Facet-filter-how-to-specify-OR-expression-tp2930570p2930570.html Sent from the Solr - U

Re: Facet filter: how to specify OR expression?

It works. Many thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/Facet-filter-how-to-specify-OR-expression-tp2930570p2930783.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Facet filter: how to specify OR expression?

I have another facet that is of type integer and it gave an exception. Is it true that the field has to be of type string or text for the OR expression to work? -- View this message in context: http://lucene.472066.n3.nabble.com/Facet-filter-how-to-specify-OR-expression-tp2930570p2930863.html

Re: Facet filter: how to specify OR expression?

The exception says: java.lang.NumberFormatExcepton: for input string "or" The field type is: -- View this message in context: http://lucene.472066.n3.nabble.com/Facet-filter-how-to-specify-OR-expression-tp2930570p2931282.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Facet filter: how to specify OR expression?

Oh I see I was wrong in using (pdf or txt). It worked, but have different meanings altogether from (pdf OR txt). Thanks a lot for your help. Best regards, Yee -- View this message in context: http://lucene.472066.n3.nabble.com/Facet-filter-how-to-specify-OR-expression-tp2930570p2931347.htm

What is the different?

Hi, I have two queries: (1) q = (change management) (2) q = (change management) AND domain_ids:(0^1.3 OR 1) The purpose of the (2) is to boost the records with domain_ids=0. In my database all records has domain_ids = 0 or 1, so domains_ids:(0 or 1) will always returns the full database. Now my

Re: Logically equivalent queries but vastly different no of results?

I think I know what it is. The second query has higher scores than the first. The additional condition "domain_ids:(0^1.3 OR 1)" which evaluates to true always - pushed up the scores and allows a LOT more records to pass. Is there a better way of doing this? Regards, Yee -- View this message in

Re: Logically equivalent queries but vastly different no of results?

Yes - I am using edismax but the reason is not obvious to me can you give me a pointer? Thanks Yee -- View this message in context: http://lucene.472066.n3.nabble.com/Logically-equivalent-queries-but-vastly-different-no-of-results-tp3190278p3199362.html Sent from the Solr - User mailing list

Multiplexing TokenFilter for multi-language?

Sorry if this has already been discussed, but I have already spent a couple of days googling in vain The problem: - documents in multiple languages (us, de, fr, es). - language is known (a team of editors determines the language manually, and users are asked to specify language option for sear

Re: Multiplexing TokenFilter for multi-language?

You are right - the stemmer was only instantiated twice. Not sure why it was instantiated twice. I tested with 10 and 50 records, maybe it was associated with the auto-commit cycle). What a bummer. Back to the drawing board again. Thanks for your input anyway. I was struggling with weird search b

Re: Multiplexing TokenFilter for multi-language?

I believe that the FilterFactory is not designed to be called for each instant of field processing. Think of it, that would be terribly inefficient. The instantiated stemmer is meant to be reused as much as possible. Maybe the FilterFactory is called to instantiate a new stemmer in association with