- Newest
- Most votes
- Most comments
Hey alextk, sorry to hear that you could not find the docs. We will continue to close gaps in supported apis/types. The following page list the current supported types.
https://docs.aws.amazon.com/keyspaces/latest/devguide/cassandra-apis.html
Could you share your model for the table and your queries?
What is the suggested alternative from AWS keyspaces instead of Frozen? If I am not wrong, avoiding Frozen leads to enormous tombstone which makes sense in my use case where the whole collection data set is updated at once and not single item in the list. Someone, can throw more light on this?
hi @sagarm
Amazon Keyspaces does not have the same performance tradeoffs for working with collections. Customers can change individual items in a collection or replace the entire collection without creating tombstones and degrading performance. Customers can expect single digit millisecond operations on row access.
depending on the collection type you can create a high carnality key so the structure gets flattened.
Nested structure
{'key':{'nestedkey':'nestedvalye'}}
to flattened structure
{'key#nestedkey':'nestedvalue'}
Alternatively, If you are replacing the entire collection on every update, then a blob will work in a similar way.
Relevant content
- asked 9 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago