techdocsmith commented on a change in pull request #11541:
URL: https://github.com/apache/druid/pull/11541#discussion_r682127049
##########
File path: docs/ingestion/data-model.md
##########
@@ -0,0 +1,38 @@
+---
+id: data-model
+title: "Druid data model"
+sidebar_label: Data model
+description: Introduces concepts of datasources, primary timestamp,
dimensions, and metrics.
+---
+
+Druid stores data in datasources, which are similar to tables in a traditional
relational database management systems (RDBMS). Druid's data model shares
similarities with both relational and timeseries data models.
+
+## Primary timestamp
+
+Druid schemas must always include a primary timestamp. Druid uses the primary
timestamp to [partition and sort](./partitioning.md) your data. Druid uses the
primary timestamp to rapidly identify and retrieve data within the time range
of queries. Druid also uses the primary timestamp column
+for time-based [data management operations](./data-management.md) such as
dropping time chunks, overwriting time chunks, and time-based retention rules.
+
+Druid parses the primary timestamp based on the
[`timestampSpec`](./ingestion-spec.md#timestampspec) configuration at ingestion
time. You can control other important operations that are based on the primary
timestamp
+[`granularitySpec`](./ingestion-spec.md#granularityspec). Regardless of the
source input field for the primary timestamp, Druid always stores the timestamp
in the `__time` column in your Druid datasource.
Review comment:
No. `granlularitySpec` controls other aspects not controlled by the
`timestampspec`. I think that this will be better to move the last sentence
starting with "Regardless to line 15 after ingestion time. Then start a new
paragraph for `granularitySpec`. I'll make this change after you push yours.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
