cassandra-rs v0.16.0 Release Notes
Release Date: 2021-03-10 // about 2 years ago-
โ Added
- ๐ฆ Exposes separate setters for collection types on
Tuple
andUserType
. As such, the respectiveset_collection
andset_collection_by_name
on both types have been removed.set_collection
becomesset_set
andset_collection_by_name
becomesset_set_by_name
.- Added
Cluster::set_token_aware_routing_shuffle_replicas
.
- Added
- ๐
ConstDataType::new_user_type
has been added, to allow the creation of a user data type from an existing data type. - Added
Session::execute_with_payloads
andSession::execute_batch_with_payloads
to allow getting custom payloads from query and batch executions.
๐ฅ Breaking changes
- Extended the lifetime of a
CassResult
into aRow
. This is a breaking change, and may require reworking the code to satisfy the lifetime requirement that theCassResult
must live longer than theRow
. CassCollection::new
has been renamed toCassCollection::with_capacity
, andCassCollection::new
has been created, that no longer requires a capacity. This closely mirrors the API that the standard library collections expose, and that theitem_count
passed tonew
is merely a capacity hint for the purpose of optimization.time::Duration
has been replaced withstd::time::Duration
.
๐ Changed
- ๐ Change various functions to avoid the extra overhead using an intermediate CString object.
- ๐ Switched to using
parking_lot::Mutex
instead ofstd::sync::Mutex
forCassFuture
coordination. - Implemented
size_hint
onResultIterator
. - โฌ๏ธ Bumped versions of various dependencies.
๐ Fixed
CassResult::set_paging_state_token
was implemented incorrectly, namely, it did nothing, and has instead been replaced withCassResult::paging_state_token
.Statement::set_paging_state_token
has been changed to take a&[u8]
instead of a&str
, as a paging state token isn't necessarily utf8 encoded.
- ๐ฆ Exposes separate setters for collection types on