Pycassa

The main change to be aware of for this release is the new no-retry behavior
for counter operations. If you have been maintaining a separate connection
pool with retries disabled for usage with counters, you may discontinue that
practice after upgrading.

Features

By default, counter operations will not be retried automatically. This
makes it easier to use a single connection pool without worrying about
overcounting.

Bug Fixes

* Don’t remove entire row when an empty list is supplied for the columns
parameter of remove() or the batch remove methods.
* Add python-setuptools to debian build dependencies
* Batch remove() was not removing subcolumns when the specified supercolumn
was 0 or other “falsey” values
* Don’t request an extra row when reading fewer than buffer_size rows with
get_range() or get_indexed_slices().
* Remove pool_type from logs, which showed up as None in recent versions
* Logs were erroneously showing the same server for retries of failed
operations even when the actual server being queried had changed

This release is primarily a bugfix release with a couple
of minor features and removed deprecated items.

Features

* Accept column_validation_classes when creating or altering
column families with SystemManager
* Ignore UNREACHABLE nodes when waiting for schema version
agreement

Bug Fixes

* Remove accidental print statement in SystemManager
* Raise TypeError when unexpected types are used for
comparator or validator types when creating or altering
a Column Family
* Fix packing of column values using column-specific validators
during batch inserts when the column name is changed by packing
* Always return timestamps from inserts
* Fix NameError when timestamps are used where a DateType is
expected
* Fix NameError in python 2.4 when unpacking DateType objects
* Handle reading composites with trailing components
missing
* Upgrade ez_setup.py to fix broken setuptools link

Removed Deprecated Items

The following items have been removed:

* pycassa.connect()
* pycassa.connect_thread_local()
* ConnectionPool.status()
* ConnectionPool.recreate()

This release adds full compatibility with Cassandra 1.0 and removes support
for schema manipulation in Cassandra 0.7.

In this release, schema manipulation should work with Cassandra 0.8 and 1.0,
but not 0.7. The data API should continue to work with all three versions.

Bug Fixes

* Don’t ignore columns parameter in ColumnFamilyMap.insert()
* Handle empty instance fields in ColumnFamilyMap.insert()
* Use the same default for timeout in pycassa.connect() as ConnectionPool
uses
* Fix typo which caused a different exception to be thrown when an
AllServersUnavailable exception was raised
* IPython 0.11 compatibility in pycassaShell
* Correct dependency declaration in setup.py
* Add UUIDType to supported types

Features

The filter_empty parameter was added to get_range() with a default of True;
this allows empty rows to be kept if desired

Deprecated

pycassa.connect()
pycassa.connect_thread_local()

This is strictly a bug-fix release addressing a few issues created in 1.2.0.

Bug Fixes

* Correctly check for Counters in ColumnFamily when setting
default_validation_class
* Pass kwargs in ColumnFamilyMap to ColumnFamily
* Avoid potential UnboundLocal in ConnectionPool.execute() when get() fails
* Fix ez_setup dependency/bundling so that package installations using
easy_install or pip don’t fail without ez_setup installed

This should be a fairly smooth upgrade from pycassa 1.1. The
primary changes that may introduce minor incompatibilities are
the changes to ColumnFamilyMap and the automatic skipping of
"ghost ranges" in .ColumnFamily.get_range().

Features

* Add ConnectionPool.fill()
* Add FloatType, DoubleType, DateType, and BooleanType support.
* Add CompositeType support for static composites. See "Composite Types"
for more details.
* Add timestamp, ttl to ColumnFamilyMap.insert() params
* Support variable-length integers with IntegerType. This allows more
space-efficient small integers as well as integers that exceed the size
of a long.
* Make ColumnFamilyMap a subclass of ColumnFamily instead of using one
as a component. This allows all of the normal adjustments normally done
to a ColumnFamily to be done to a ColumnFamilyMap instead. See "Class
Mapping with Column Family Map" for examples of using the new version.
* Expose the following ConnectionPool attributes, allowing them to be
altered after creation: max_overflow, pool_timeout, recycle,
max_retries, and logging_name. Previously, these were all supplied as
constructor arguments. Now, the preferred way to set them is to alter
the attributes after creation. (However, they may still be set in the
constructor by using keyword arguments.)
* Automatically skip "ghost ranges" in ColumnFamily.get_range().
Rows without any columns will not be returned by the generator,
and these rows will not count towards the supplied row_count.

Bug Fixes

* Add connections to ConnectionPool more readily when prefill is False.
Before this change, if the ConnectionPool was created with prefill=False,
connections would only be added to the pool when there was concurrent
demand for connections. After this change, if prefill=False and
pool_size=N, the first N operations will each result in a new connection
being added to the pool.
* Close connection and adjust the ConnectionPool‘s connection count after a
TApplicationException. This exception generally indicates programmer error,
so it’s not extremely common.
* Handle typed keys that evaluate to False

Deprecated

* ConnectionPool.recreate()
* ConnectionPool.status()

Miscellaneous

* Better failure messages for ConnectionPool failures
* More efficient packing and unpacking
* More efficient multi-column inserts in ColumnFamily.insert() and
ColumnFamily.batch_insert()
* Prefer Python 2.7’s collections.OrderedDict over the bundled version when
available

Features

* Add max_count and column_reversed params to get_count()
* Add max_count and column_reversed params to multiget_count()

Bug Fixes

* Don’t retry operations after a TApplicationException. This exception is
reserved for programmatic errors (such as a bad API parameters), so
retries are not needed.
* If the read_consistency_level kwarg was used in a ColumnFamily
constructor, it would be ignored, resulting in a default read
consistency level of ONE. This did not affect the read consistency
level if it was specified in any other way, including per-method or by
setting the read_consistency_level attribute.