Sorting on a non-integer has space problems. As I understand it, sorting creates an array of integers the size of the number of records in the entire index. Sorting on a non-integer type also creates a separate array of the same size with the field data copied into it. Thus sorting a non-integer field can use several times as much memory.
We have a very large index with very small records. We are creating matching integer fields for various fields just to have faster sorts, and we are doing this after benchmarking our speed and space behaviours. I filed a Jira issue: https://issues.apache.org/jira/browse/SOLR-464 Thanks for your time, Lance Norskog -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik Seeley Sent: Thursday, January 17, 2008 2:53 PM To: solr-user@lucene.apache.org Subject: Re: copyField limitation On Jan 17, 2008 4:53 PM, Lance Norskog <[EMAIL PROTECTED]> wrote: > Because sort works much faster on type 'integer', but range queries do > not work on type 'integer', Really? The sort speed should be identical. -Yonik
