12.0.0b7 (2021-05-11)
Breaking
- The
account_url
parameter in the client constructors has been renamed toendpoint
. - The
TableEntity
object now acts exclusively like a dictionary, and no longer supports key access via attributes. - Metadata of an entity is now accessed via
TableEntity.metadata
attribute rather than a method. - Removed explicit
LinearRetry
andExponentialRetry
in favor of keyword parameter. - Renamed
filter
parameter in query APIs toquery_filter
. - The
location_mode
attribute on clients is now read-only. This has been added as a keyword parameter to the constructor. - The
TableItem.table_name
has been renamed toTableItem.name
. - Removed the
TableClient.create_batch
method along with theTableBatchOperations
object. The transactional batching is now supported via a simple Python list of tuples. TableClient.send_batch
has been renamed toTableClient.submit_transaction
.- Removed
BatchTransactionResult
object in favor of returning an iterable of batched entities with returned metadata. - Removed Batching context-manager behavior
EntityProperty
is now a NampedTuple, and can be represented by a tuple of(entity, EdmType)
.- Renamed
EntityProperty.type
toEntityProperty.edm_type
. BatchErrorException
has been renamed toTableTransactionError
.- The
location_mode
is no longer a public attribute on the Clients. - The only supported credentials are
AzureNamedKeyCredential
,AzureSasCredential
, or authentication by connection string - Removed
date
andapi_version
from theTableItem
class.
Fixes
- Fixed issue with Cosmos merge operations.
- Removed legacy Storage policies from pipeline.
- Removed unused legacy client-side encryption attributes from client classes.
- Fixed sharing of pipeline between service/table clients.
- Added support for Azurite storage emulator
- Throws a
RequestTooLargeError
on transaction requests that return a 413 error code - Added support for Int64 and Binary types in query filters
- Added support for
select
keyword parameter toTableClient.get_entity()
. - On
update_entity
anddelete_entity
if noetag
is supplied via kwargs, theetag
in the entity will be used if it is in the entity.