cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyler Hobbs <ty...@datastax.com>
Subject Re: Working with legacy data via CQL
Date Sat, 15 Nov 2014 00:24:29 GMT
What version of cassandra did you originally create the column family in?
Have you made any schema changes to it through cql or cassandra-cli, or has
it always been exactly the same?

On Wed, Nov 12, 2014 at 2:06 AM, Erik Forsberg <forsberg@opera.com> wrote:

> On 2014-11-11 19:40, Alex Popescu wrote:
> > On Tuesday, November 11, 2014, Erik Forsberg <forsberg@opera.com
> > <mailto:forsberg@opera.com>> wrote:
> >
> >
> > You'll have better chances to get an answer about the Python driver on
> > its own mailing
> > list
> https://groups.google.com/a/lists.datastax.com/forum/#!forum/python-driver-user
>
> As I said, this also happens when using cqlsh:
>
> cqlsh:test> SELECT column1,value from "Users" where key =
> a6b07340-047c-4d4c-9a02-1b59eabf611c and column1 = 'date_created';
>
>  column1      | value
> --------------+------------------------------
>  date_created | '\x00\x00\x00\x00Ta\xf3\xe0'
>
> (1 rows)
>
> Failed to decode value '\x00\x00\x00\x00Ta\xf3\xe0' (for column 'value')
> as text: 'utf8' codec can't decode byte 0xf3 in position 6: unexpected
> end of data
>
> So let me rephrase: How do I work with data where the table has metadata
> that makes some columns differ from the main validation class? From
> cqlsh, or the python driver, or any driver?
>
> Thanks,
> \EF
>



-- 
Tyler Hobbs
DataStax <http://datastax.com/>

Mime
View raw message