2 回答
- 最新
- 投票最多
- 评论最多
0
please refer - https://repost.aws/questions/QU4Baa0YKsQguMOYP-rzbWIw/choosing-timestream-dimension-and-query-performance
0
In our use-case, the only filter that is constant across all queries is the tenant
dimension, but whenever there will be a scenario of filtering on that additional filterDimension
column with higher number of matching values, we are encountering higher query latencies. This additional filterDimension
cannot be included in the custom partitioning keys since it only allows one dimension currently, which will be tenant
for us. So what will be the possible solution for this particular scenario?
已回答 3 个月前
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前