You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by fj...@apache.org on 2019/02/01 22:21:18 UTC

[incubator-druid] branch master updated: lol (#6985)

This is an automated email from the ASF dual-hosted git repository.

fjy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git


The following commit(s) were added to refs/heads/master by this push:
     new 6430ef8  lol (#6985)
6430ef8 is described below

commit 6430ef8e1b62515576f5c7ec090bcd79da7eb8ee
Author: Justin Borromeo <jb...@edu.uwaterloo.ca>
AuthorDate: Fri Feb 1 14:21:13 2019 -0800

    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 0408a39..58f0fae 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


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org