From 6430ef8e1b62515576f5c7ec090bcd79da7eb8ee Mon Sep 17 00:00:00 2001 From: Justin Borromeo Date: Fri, 1 Feb 2019 14:21:13 -0800 Subject: [PATCH] lol (#6985) --- docs/content/ingestion/schema-design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/ingestion/schema-design.md b/docs/content/ingestion/schema-design.md index 0408a39330a..58f0faeca08 100644 --- a/docs/content/ingestion/schema-design.md +++ b/docs/content/ingestion/schema-design.md @@ -86,7 +86,7 @@ rollup and load your existing data as-is. Rollup in Druid is similar to creating (Like OpenTSDB or InfluxDB.) Similar to time series databases, Druid's data model requires a timestamp. Druid is not a timeseries database, but -it is a natural choice for storing timeseries data. Its flexible data mdoel allows it to store both timeseries and +it is a natural choice for storing timeseries data. Its flexible data model allows it to store both timeseries and non-timeseries data, even in the same datasource. To achieve best-case compression and query performance in Druid for timeseries data, it is important to partition and