On 7/15/06, Rob Staveley (Tom) <[EMAIL PROTECTED]> wrote:
The problem one is
testSortingReverseNullFirst. My reckoning is that you are forward-sorting
(or ascending-sorting if that's the right thing to say) the non-nulls.
OK, examples are probably easier to work with.
If we have a list of [A,nu
---
From: Yonik Seeley [mailto:[EMAIL PROTECTED]
Sent: 15 July 2006 16:52
To: java-user@lucene.apache.org
Subject: Re: MissingStringLastComparatorSource and MultiSearcher
On 7/15/06, Rob Staveley (Tom) <[EMAIL PROTECTED]> wrote:
> Incidentally, Yonik, is the logic for
> org.apache.solr
ult.doc(6).get("id"));
assertEquals("wrong order 7", "1", result.doc(7).get("id"));
}
8<
-Original Message-
From: Yonik Seeley [mailto:[EMAIL PROTECTED]
Sent: 14 July 2006 21:59
To: java-user@lucene.apache.org
Subject: Re:
t;, "1", result.doc(7).get("id"));
}
8<
-Original Message-
From: Yonik Seeley [mailto:[EMAIL PROTECTED]
Sent: 14 July 2006 21:59
To: java-user@lucene.apache.org
Subject: Re: MissingStringLastComparatorSource and MultiSearcher
On 7/14/06, Rob Staveley (Tom) <[EMAIL PROTECTE
m not sure if it wouldn't be better for it to be
SortField.FLOAT in the above.
-Original Message-
From: Yonik Seeley [mailto:[EMAIL PROTECTED]
Sent: 14 July 2006 21:59
To: java-user@lucene.apache.org
Subject: Re: MissingStringLastComparatorSource and MultiSearcher
On 7/14/06, Rob
-user@lucene.apache.org
Subject: RE: MissingStringLastComparatorSource and MultiSearcher
: I was wanting to apply this to a field, which sorts on INT. Specifically
I'm
: trying to achieve reverse chronological sorting on a timestamp field,
which
: stores YYMMDDHHI (i.e. resolves to 10 minutes and does
: I was wanting to apply this to a field, which sorts on INT. Specifically I'm
: trying to achieve reverse chronological sorting on a timestamp field, which
: stores YYMMDDHHI (i.e. resolves to 10 minutes and doesn't handle centuries).
: Missing timestamps are assumed to be "old" (i.e. should appe
On 7/14/06, Rob Staveley (Tom) <[EMAIL PROTECTED]> wrote:
I was wanting to apply this to a field, which sorts on INT.
The problem with int is that the FieldCache stores the values as an
int[], and you can't tell when a value is missing.
Specifically I'm
trying to achieve reverse chronological
ean
reverse, boolean nullLast, boolean nullFirst) {
// ...
}
}
and handling all feasible SortField types?
-Original Message-
From: Yonik Seeley [mailto:[EMAIL PROTECTED]
Sent: 14 July 2006 18:30
To: java-user@lucene.apache.org
Subject: Re: MissingStringLastComparatorSource and Mu
On 7/14/06, Rob Staveley (Tom) <[EMAIL PROTECTED]> wrote:
Chris Hostetter and Yonik's MissingStringLastComparator looks like a neat
way to specify where to put null values when you want them to appear at the
end of reverse sorts rather than at the beginning, but I spotted the note...
// Note
Chris Hostetter and Yonik's MissingStringLastComparator looks like a neat
way to specify where to put null values when you want them to appear at the
end of reverse sorts rather than at the beginning, but I spotted the note...
// Note: basing lastStringValue on the StringIndex won't work
/
11 matches
Mail list logo
