Wei:
That is odd. These should be the same so I'm puzzled too.
I'm assuming that you're using the exact same schema on both with each
field having the exact same definitions. And since you say it's the
same release of Solr it's not like some default changed
Here's an idea (and I'm shooting i
Thanks Erick. However our indexes on stand alone and cloud are both static
-- we indexed them from the same source xmls, optimize and have no updates
after it is done. Also in cloud there is only one single shard( with
multiple replicas ). I assume distributed stats doesn't have effect in this
case
2018 21:19
> To: solr-user
> Subject: Re: Different solr score between stand alone vs cloud mode solr
>
> Short form:
>
> As docs are updated, they're marked as deleted until the segment is
> merged. This affects things like term frequency and doc frequency
> which i
Also the score is a fluid number, you shouldnt use the score for any real
reason aside from seeing that the documents are in the right order in
relation to the scores from the other documents in the result set. or the
occasional condition where two results switch in place from one to the
other bec
Short form:
As docs are updated, they're marked as deleted until the segment is
merged. This affects things like term frequency and doc frequency
which in turn influences the score.
Due to how commits happen, i.e. autocommit will hit at slightly skewed
wall-clock time, different segments are merg
Hi,
Recently we have an observation that really puzzled us. We have two
instances of Solr, one in stand alone mode and one is a single-shard solr
cloud with a couple of replicas. Both are indexed with the same documents
and have same solr version 6.6.2. When issue the same query, the solr
scor
