Menu

Dynoxide 1.5.0 release notes
📰

Dynoxide 1.5.0 release notes

DEV Community: rust·Martin Hicks·3 days ago
#5YRIo3fm
#devtorust#devto#dev#dynoxide#records
Reading 0:00
15s threshold

Dynoxide 1.5.0 is out, two days after 1.4.0 . The vector fixes came out of Parity Suite, and I wrote up the billing change earlier today, so this one's just the list.

The crate moves to dynoxide-rs 3.2.0. Everything else you install is 1.5.0.

Behaviour changes

A read of a table with a vector index is charged on the billed size. DynamoDB now bills a vector at 4 bytes per dimension on reads as well as writes, so an item whose numbers take it over a 4KB boundary costs a unit less. That covers GetItem , BatchGetItem , TransactGetItems , Query , Scan and PartiQL reads. A read from a secondary index and the 400KB item limit still use the stored size ( #264 ).

GetItem and TransactGetItems charge for the whole item , whatever the projection returns, as BatchGetItem and DynamoDB already did.

Stream SequenceNumber s are 21 digits , within DynamoDB's range of 21 to 40. Records already in a database file show in the same form.

GetShardIterator validates SequenceNumber .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.