InvalidQueryException: Frozen nested collections are not yet supported

0

Hi,

looks like frozen nested collection are not supported on AWS keyspaces.
Is there any documentation about this issue anywhere?
I could not find it in the AWS keyspaces - Apache cassandra compatibility notes.

alextk
已提问 3 年前401 查看次数
3 回答
0
已接受的回答

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?

已回答 3 年前
0

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?

sagarm
已回答 3 年前
0

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.

已回答 3 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则