Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 81299 invoked from network); 26 Jun 2010 05:53:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Jun 2010 05:53:42 -0000 Received: (qmail 82420 invoked by uid 500); 26 Jun 2010 05:53:41 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 82146 invoked by uid 500); 26 Jun 2010 05:53:38 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 82138 invoked by uid 99); 26 Jun 2010 05:53:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jun 2010 05:53:37 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.161.44] (HELO mail-fx0-f44.google.com) (209.85.161.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jun 2010 05:53:30 +0000 Received: by fxm16 with SMTP id 16so463156fxm.31 for ; Fri, 25 Jun 2010 22:53:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.191.196 with SMTP id c4mr121604hbi.106.1277531588890; Fri, 25 Jun 2010 22:53:08 -0700 (PDT) Received: by 10.239.182.5 with HTTP; Fri, 25 Jun 2010 22:53:08 -0700 (PDT) Date: Sat, 26 Jun 2010 17:53:08 +1200 Message-ID: Subject: sstable2json and key ordering From: Todd Nine To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001636457d1e8b8f7e0489e8806d --001636457d1e8b8f7e0489e8806d Content-Type: text/plain; charset=ISO-8859-1 Hi all, I'm having a lot of problems getting Lucandra to correctly handle numeric document fields. After examining the keys it has written to the CF, I believe it may be an issue of column ordering by bytes. After dumping the CF with the test data using sstable2json, the keys are in opposite order of what the current indexReader is expecting for seeking numeric values, however it is correct when seeking text values. My question is, when I dump a CF via sstable2json, are the keys from top to bottom of the output file the same order as what Cassandra will scan when a KeyRange is given? In other words, does a key range scan from "top" to the "bottom" of the keys when you are viewing them in the json? Thanks, Todd --001636457d1e8b8f7e0489e8806d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,
=A0=A0I'm having a lot of problems getting Lucandra to corr= ectly handle numeric document fields. =A0 After examining the keys it has w= ritten to the CF, I believe it may be an issue of column ordering by bytes.= =A0After dumping the CF with the test data using sstable2json, the keys ar= e in opposite order of what the current indexReader is expecting for seekin= g numeric values, however it is correct when seeking text values. =A0My que= stion is, when I dump a CF via sstable2json, are the keys from top to botto= m of the output file the same order as what Cassandra will scan when a KeyR= ange is given? =A0In other words, does a key range scan from "top"= ; to the "bottom" of the keys when you are viewing them in the js= on?

Thanks,
Todd
--001636457d1e8b8f7e0489e8806d--