2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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?
répondu il y a 3 ans
Contenus pertinents
demandé il y a 2 ans
demandé il y a 2 ans
demandé il y a 3 ans
demandé il y a un an
