2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
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?
respondido hace 3 años
Contenido relevante
preguntada hace 8 meses
preguntada hace 9 meses
preguntada hace 10 meses
preguntada hace 10 meses
