Ok. Thank you Chris.
It is a custom Query parser.
I will check my Query parser on where it inject the slop 1.
On Tue, Jun 16, 2015 at 3:26 AM, Chris Hostetter
wrote:
>
> : I encounter this peculiar case with solr 4.10.2 where the parsed query
> : doesnt seem to be logical.
> :
> : PHRASE23("redu
Hi,
I encounter this peculiar case with solr 4.10.2 where the parsed query
doesnt seem to be logical.
PHRASE23("reduce workforce") ==>
SpanNearQuery(spanNear([spanNear([Contents:reduceƤ,
Contents:workforceƤ], 1, true)], 23, true))
The question is why does the Phrase("quoted string") gets convert
Hi,
I am puzzled on the Term Frequency Behaviour of the DefaultSimilarity
implementation
I have suppressed the IDF by setting to 1.
TF-IDF would inturn reflect the same value as in Term Frequency
Below are the inferences:
Red coloured are expected to give a hit count(Term Frequency) of 2 but was
Please ignore.
On Wed, May 20, 2015 at 2:45 PM, ariya bala wrote:
> Thanks Jack.
> In my case there is only one document - Foo Foo is in bar
> As per your comment, I should expect TF to be 2.
> But I am getting one.
> Is there any check where if one match is a subset of other
Thanks Jack.
In my case there is only one document - Foo Foo is in bar
As per your comment, I should expect TF to be 2.
But I am getting one.
Is there any check where if one match is a subset of other, is calculated
once?
My class extends DefaultSimilarity.
Cheers
Ariya Bala S
On Wed, May 20
Hi,
I have made custom class for scoring the similarity
(TermFrequencyBiasedSimilarity).
The score was deduced by considering just the TF part (acheived by setting
IDF=1).
Question is:
-
*Document content:* Foo Foo is in bar
*Search query:* Foo bar
*slop:* 3
With Slop 3, There ar
Hi,
I am facing an issue (solr 4.10.2) when we are trying retrieve a document
and highlight the hits.
Below is the exception and this happens in a random fashion.
If we try again to reload the same document which threw this exception, it
loads without exception.
Any help would be appreciated.
*E
Hi Norgorn,
I think there is no ready-made tool out of the box, but you have the spare
parts in the MapreduceIndexerTool :-)
With little effort you can decouple the index merging component from
MRIndexerTool and use based on the needs.
I did the same.
On Fri, Apr 17, 2015 at 10:40 AM, Norgorn wr