This was fixed April 24th
https://issues.apache.org/jira/browse/SOLR-1124
explained further in
https://issues.apache.org/jira/browse/SOLR-
-Yonik
http://www.lucidimagination.com
On Thu, Mar 26, 2009 at 10:24 PM, Asif Rahman wrote:
>
> Hi all,
>
> I'm having an issue with the order of my re
I have been intending to although I have been dragging my feet on it. I've
never opened a bug before so I'm not sure of the protocol. If you don't
mind, it would be great if you could send me a pm and point me in the right
direction.
Thanks,
Asif
On Mon, May 18, 2009 at 7:30 PM, Ensdorf Ken
>
> A Unit test would be ideal, but even if you can just provide a list of
> steps (ie: using this solrconfig+schema, index these docs, then update
> this one doc, then execute this search) it can help people track things
> down.
>
> Please open a bug and attach as much detail as you can there.
>
>
: Any documents marked deleted in this index are just the result of updates to
: those documents. There are no purely deleted documents. Furthermore, the
: field that I am ordering by in my function query remains untouched over the
: updates.
it doesn't matter wether it was an update or a true
Hi Otis,
Any documents marked deleted in this index are just the result of updates to
those documents. There are no purely deleted documents. Furthermore, the
field that I am ordering by in my function query remains untouched over the
updates.
I've read in other posts that the logic used by th
Asif,
Could it have something to do with the deleted documents in your unoptimized
index? There documents are only marked as deleted. When you run optimize you
really remove them completely. It could be that they are getting counted by
something and that messes up the scoring/order.
Otis
