2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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?
con risposta 4 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa