You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by ca...@codespot.com on 2011/10/08 01:24:55 UTC

[cassandra-dbapi2] push by pcannon - allow override of SchemaDecoder... on 2011-10-07 23:11 GMT

Revision: d31c412df1a6
Author:   paul cannon <pa...@riptano.com>
Date:     Fri Oct  7 16:06:33 2011
Log:      allow override of SchemaDecoder

When an execute() call is made, there will likely be cases where the
caller knows better than the driver how best to deserialize data- I
guess this is the point to the ASSUME command in cassandra-cli and which
has been requested for cqlsh.

The simplest way to allow caller-controlled deserialization, it seems to
me, is to allow passing in a SchemaDecoder-like class as an optional
parameter to execute(). The custom decoder will be used until a new
query is made.

This adds that.

http://code.google.com/a/apache-extras.org/p/cassandra-dbapi2/source/detail?r=d31c412df1a6