It is also possible to sort by function. This allows you to avoid
storing an array of 1 int for all documents. It is slower than the raw
Lucene sort.
On Wed, Aug 25, 2010 at 1:46 AM, Toke Eskildsen
wrote:
> On Wed, 2010-08-25 at 07:16 +0200, Shelly_Singh wrote:
>> I have 1 bln documents to sort.
On Wed, 2010-08-25 at 07:16 +0200, Shelly_Singh wrote:
> I have 1 bln documents to sort. So, that would mean ( 8 bln bytes == 8GB RAM)
> bytes.
> All I have is 8 GB on my machine, so I do not think approach would work.
This implies that your numeric value can be more than 2 billion. Are you
sure
19, 2010 7:18 PM
> To: java-user@lucene.apache.org
> Subject: Re: Sorting a Lucene index
>
> You haven't yet told us how many documents you're talking about here, so
> it's
> hard to have a good idea of what solutions are. That said, I'd just try
> sorting f
:18 PM
To: java-user@lucene.apache.org
Subject: Re: Sorting a Lucene index
You haven't yet told us how many documents you're talking about here, so
it's
hard to have a good idea of what solutions are. That said, I'd just try
sorting first.
The sorting cache size will be something
[mailto:ansh...@gmail.com]
> Sent: Wednesday, August 18, 2010 5:21 PM
> To: java-user@lucene.apache.org
> Subject: Re: Sorting a Lucene index
>
> Hi Shelly,
> The search results so returned are sorted either by relevance, index order,
> stored field, or custom order.
> As yo
shelly_si...@infosys.com
> Phone: (M) 91 992 369 7200, (VoIP)2022978622
>
> -Original Message-
> From: Anshum [mailto:ansh...@gmail.com]
> Sent: Wednesday, August 18, 2010 5:21 PM
> To: java-user@lucene.apache.org
> Subject: Re: Sorting a Lucene index
>
> Hi S
: shelly_si...@infosys.com
Phone: (M) 91 992 369 7200, (VoIP)2022978622
-Original Message-
From: Anshum [mailto:ansh...@gmail.com]
Sent: Wednesday, August 18, 2010 5:21 PM
To: java-user@lucene.apache.org
Subject: Re: Sorting a Lucene index
Hi Shelly,
The search results so returned are
Hi Shelly,
The search results so returned are sorted either by relevance, index order,
stored field, or custom order.
As you are saying that you would not be able to maintain the index order,
you would have to do the sort at run time.
Sorting on a stored field is not costly and you may use it comf
Hi,
I have a Lucene index that contains a numeric field along with certain other
fields. The order of incoming documents is random and un-predictable. As a
result, while creating an index, I end up adding docs in random order with
respect to the numeric field value.
For example, documents may
