On Thu, Nov 17, 2011 at 6:59 AM, Chris Hostetter
wrote:
>
> : 1. "omitTermFreqAndPositions" is very straightforward but if I avoid
> : positions I'll refuse to serve phrase queries. I had searched for this in
>
> but do you really need phrase queries on your "cat" field? i thought the
> point wa
: 1. "omitTermFreqAndPositions" is very straightforward but if I avoid
: positions I'll refuse to serve phrase queries. I had searched for this in
but do you really need phrase queries on your "cat" field? i thought the
point was to have simple matching on those terms?
: 2. Function query se
: 1. "omitTermFreqAndPositions" is very straightforward but if I avoid
: positions I'll refuse to serve phrase queries. I had searched for this in
but do you really need phrase queries on your "cat" field? i thought the
point was to have simple matching on those terms?
: 2. Function query se
No solutions to the problem?
OK. I'll look for the changes in source code and if I succeed I'll share it
here for feedback.
Thanks
On Tue, Nov 8, 2011 at 5:06 PM, Samarendra Pratap wrote:
> Hi Chris,
> Thanks for the insight.
>
> 1. "omitTermFreqAndPositions" is very straightforward but if I
Hi Chris,
Thanks for the insight.
1. "omitTermFreqAndPositions" is very straightforward but if I avoid
positions I'll refuse to serve phrase queries. I had searched for this in
past as well but I finally reached to the conclusion that there is no thing
like "omitTermFreq" (only). Perhaps because
: You can write your custom similarity implementation, and override the
: /lengthNorm()/ method to return a constant value.
The postered already said (twice!) that they have already set
omitNorms=true, so lengthNorm won't even be used
omiting norms (or mucking with norms by modifying the lengt
Hi Samar,
You can write your custom similarity implementation, and override the
/lengthNorm()/ method to return a constant value.
Then in your /schema.xml/ specify your custom implementation as the default
similarity class.
But you need to rebuild your index from scratch for this to come into
ef
Hi Pravesh, thanks for your reply but I am not asking about the "omitNorms"
(index time parameter) I am asking about how to consider multiple matches
of a term in a single field as "one" during query time.
Thanks
On Mon, Nov 7, 2011 at 2:48 PM, pravesh wrote:
> Did you rebuild the index from s
Did you rebuild the index from scratch. Since this is index time factor, you
need to build complete index from scratch.
Regds
Pravesh
--
View this message in context:
http://lucene.472066.n3.nabble.com/to-prevent-number-of-matching-terms-in-contributing-score-tp3486373p3486447.html
Sent from the
