Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 33955 invoked from network); 2 May 2010 14:35:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 May 2010 14:35:18 -0000 Received: (qmail 91553 invoked by uid 500); 2 May 2010 14:35:17 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 91511 invoked by uid 500); 2 May 2010 14:35:17 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 91504 invoked by uid 99); 2 May 2010 14:35:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 May 2010 14:35:17 +0000 X-ASF-Spam-Status: No, hits=-1377.5 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 May 2010 14:35:16 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o42EYu8W020190 for ; Sun, 2 May 2010 14:34:56 GMT Message-ID: <20857241.5421272810895985.JavaMail.jira@thor> Date: Sun, 2 May 2010 10:34:55 -0400 (EDT) From: "Robert Muir (JIRA)" To: dev@lucene.apache.org Subject: [jira] Commented: (LUCENE-2426) change sort order to binary order In-Reply-To: <20408154.5401272810055637.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LUCENE-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863137#action_12863137 ] Robert Muir commented on LUCENE-2426: ------------------------------------- by the way: as mentioned above, as far as numerics and collation goes, both of these today avoid any of the parts of unicode that are sensitive to such a sort order change. So these already "backwards compatible" in the sense that numeric fields or collated fields will sort the same way in either UTF-8/UTF-32 byte[] order or UTF-16 char[] order. > change sort order to binary order > --------------------------------- > > Key: LUCENE-2426 > URL: https://issues.apache.org/jira/browse/LUCENE-2426 > Project: Lucene - Java > Issue Type: Improvement > Components: Index > Affects Versions: 4.0.0 > Reporter: Robert Muir > Fix For: 4.0.0 > > > Since flexible indexing, terms are now represented as byte[], but for backwards compatibility reasons, they are not sorted as byte[], but instead as if they were char[]. > I think its time to look at sorting terms as byte[]... this would yield the following improvements: > * terms are more opaque by default, they are byte[] and sort as byte[]. I think this would make lucene friendlier to customizations. > * numerics and collation are then free to use their own encoding (full byte) rather than avoiding the use of certain bits to remain compatible with char[] sort order. > * automaton gets simpler because as in LUCENE-2265, it uses byte[] too, and has special hacks because terms are sorted as char[] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org