Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 209.85.212.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=gi83kpU8+9Y+JNYixdCXW3xRNXoyNeir+c9YYBvBLKtEgo6uxiulG18bCoPVSFcqp0
         x9Ywu8KBwsqYuv5Ri/rtLJG3hB6oLRh1V526ahjXoNEeLWyM4tmb7ZY3RA3cG/SvJI3F
         dkqxVv1iQY6peiUrMpaYWq/Pic3iiGayQa9FQ=
MIME-Version: 1.0
In-Reply-To: 
 <2E615361C20CC44E99D51DA8E981F77472085A9BFA@GVW1362EXC.americas.hpqcorp.net>
References: 
 <2E615361C20CC44E99D51DA8E981F77472085A9B48@GVW1362EXC.americas.hpqcorp.net>
 <2E615361C20CC44E99D51DA8E981F77472085A9BFA@GVW1362EXC.americas.hpqcorp.net>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Thu, 7 Apr 2011 20:56:51 -0500
Message-ID: <BANLkTiktBMZ0NL6ce9-mpJpbww=AMdP=mw@mail.gmail.com>
Subject: Re: Secondary Index Updates Break CLI and Client Code Reading ::
 DebugLog Attached
To: user@cassandra.apache.org
Cc: "Fryar, Dexter" <dexter.fryar@hp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Addressed on the issue you created,
https://issues.apache.org/jira/browse/CASSANDRA-2436.

On Thu, Apr 7, 2011 at 12:19 PM, Fryar, Dexter <dexter.fryar@hp.com> wrote:
> I have also attached the debug log with each step attached. I've even tri=
ed going back and updating the CF with the old index to no avail. You can i=
nsert/write all you want, but reads will fail if you come across a row that=
 included one of these cases.
>
> log4j-server.properties
> =A0 =A0 =A0 =A0log4j.rootLogger=3DDEBUG,stdout,R
>
>
>
> -----Original Message-----
> From: Fryar, Dexter
> Sent: Thursday, April 07, 2011 11:19 AM
> To: user@cassandra.apache.org
> Subject: Secondary Index Updates Break CLI and Client Code Reading
>
> Creating an index, validator, and default validator then renaming/droppin=
g the index later results in read errors.
>
>
> Is there an easy way around this problem without having to keep an invali=
d definition for a column that will get deleted or expired?
>
>
> 1) create a secondary index on a column with a validator and a default va=
lidator
> 2) insert a row
> 3) read and verify the row
> 4) update the CF/index/name/validator
> 5) read the CF and get an error (CLI or Pycassa)
>
>
> CLI Commands to create the row and CF/Index
>
> create column family cf_testing with comparator=3DUTF8Type and default_va=
lidation_class=3DUTF8Type and column_metadata=3D[{column_name: colour, vali=
dation_class: LongType, index_type: KEYS}];
>
> set cf_testing['key']['colour']=3D'1234';
> list cf_testing;
>
> update column family cf_testing with comparator=3DUTF8Type and default_va=
lidation_class=3DUTF8Type and column_metadata=3D[{column_name: color, valid=
ation_class: LongType, index_type: KEYS}];
>
>
> ERROR from the CLI:
>
> list cf_testing;
> Using default limit of 100
> -------------------
> RowKey: key
> invalid UTF8 bytes 00000000000004d2
>
>
>
> Here is the Pycassa client code that shows this error too.
>
>
> badindex.py
>
> #!/usr/local/bin/python2.7
>
> import pycassa
> import uuid
> import sys
>
> def main():
> =A0try:
> =A0 =A0keyspace=3D"badindex"
> =A0 =A0serverPoolList =3D ['localhost:9160']
> =A0 =A0pool =3D pycassa.connect(keyspace, serverPoolList)
> =A0except:
> =A0 =A0print "couldn't get a connection"
> =A0 =A0sys.exit()
>
> =A0cfname=3D"cf_testing"
> =A0cf =3D pycassa.ColumnFamily(pool, cfname)
> =A0results =3D cf.get_range(start=3D'key', finish=3D'key', row_count=3D1)
> =A0for key, columns in results:
> =A0 =A0print key, '=3D>', columns
>
> if __name__ =3D=3D "__main__":
> =A0main()
>


--=20
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com