英文:
Is there an alternative to logged batches on Amazon Keyspaces?
问题
我们的团队决定从自托管的Cassandra迁移到Amazon Keyspaces。在配置了Amazon Keyspaces后，我发现不支持记录批处理。在我们的解决方案中，存在多种情况需要使用记录批处理。
例如：
我们有一些表，需要传播数据，为了实现快速查询的不同主键。在这里使用记录批处理来维护所有表的一致性。
在Amazon Keyspaces中是否有这种情况的替代解决方案？
英文:
Our team decided to move with Amazon Keyspaces from self hosted Cassandra. After configured with
Amazon Keyspaces I found that logged batches are not supported. In our solution there are multiple cases where it requires to use logged batches.
Ex:
We have few tables where we are propagating data, in order to have different primary keys for fast querying. Logged batches use here to maintain consistency in all tables.
Is there any alternative solution to this type of scenario in Amazon Keyspace ?
答案1
得分: 3
抱歉，Amazon Keyspaces 不支持 LOGGED BATCH，因此您需要在应用程序内部实现逻辑以保持表的同步。您需要重试任何更新表的失败操作，如果经过 N 次尝试仍然不成功，您需要确定是需要 (a) 向其他表发出删除操作，还是 (b) 继续重试。
很遗憾，您之前并不知道 Amazon Keyspaces 的这个限制。我建议您熟悉以下文件中的其他限制：
英文:
Unfortunately with the lack of support for LOGGED BATCH in Amazon Keyspaces, you would somehow need to implement the logic within your application to keep the tables synchronised.
You would need to retry any failed updates to a table and if after N attempts it is still unsuccessful, you need to work out whether you need (a) issue deletes to the other tables, or (b) continue retrying.
It is unfortunate that you weren't aware of this limitation in Amazon Keyspaces. I would recommend familiarising yourself with other limitations in the following documents:
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论