Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add data tiering limitation for dimensions #2628

Merged
merged 2 commits into from
Aug 16, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions use-timescale/data-tiering/about-data-tiering.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,11 +88,15 @@ For more about how data tiering works, see the
native data types, but not for non-native types, such as `JSON`, `JSONB`,
and `GIS`.

* **Latency.** S3 has higher access latency than EBS however, S3 has
comparatively greater throughput for large scans. This can affect the
execution time of queries in latency-sensitive environments, especially
* **Latency.** S3 has higher access latency than EBS however, S3 has
comparatively greater throughput for large scans. This can affect the
execution time of queries in latency-sensitive environments, especially
lighter queries.

* **Number of dimensions.** You cannot use data tiering on hypertables
partitioned on more than one dimension. Make sure your hypertables is
partitioned on time only, before you enable data tiering.

## Learn more

Learn [how data tiering works][how-to].
Expand Down