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ヶ月前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 1年前