4.3 KiB

Raw Blame History

layout
doc_page

Schema Design

This page is meant to assist users in designing a schema for data to be ingested in Druid. Druid intakes denormalized data and columns are one of three types: a timestamp, a dimension, or a measure (or a metric/aggregator as they are known in Druid). This follows the standard naming convention of OLAP data.

For more detailed information:

Every row in Druid must have a timestamp. Data is always partitioned by time, and every query has a time filter. Query results can also be broken down by time buckets like minutes, hours, days, and so on.
Dimensions are fields that can be filtered on or grouped by. They are always either single Strings or arrays of Strings.
Metrics are fields that can be aggregated. They are often stored as numbers (integers or floats) but can also be stored as complex objects like HyperLogLog sketches or approximate histogram sketches.

Typical production tables (or datasources as they are known in Druid) have fewer than 100 dimensions and fewer than 100 metrics, although, based on user testimony, datasources with thousands of dimensions have been created.

Below, we outline some best practices with schema design:

High cardinality dimensions (e.g. unique IDs)

In practice, we see that exact counts for unique IDs are often not required. Storing unique IDs as a column will kill roll-up, and impact compression. Instead, storing a sketch of the number of the unique IDs seen, and using that sketch as part of aggregations, will greatly improve performance (up to orders of magnitude performance improvement), and significantly reduce storage. Druid's hyperUnique aggregator is based off of Hyperloglog and can be used for unique counts on a high cardinality dimension. For more information, see here.

Nested dimensions

At the time of this writing, Druid does not support nested dimensions. Nested dimensions need to be flattened. For example, if you have data of the following form:

{"foo":{"bar": 3}}

then before indexing it, you should transform it to:

{"foo_bar": 3}

Counting the number of ingested events

A count aggregator at ingestion time can be used to count the number of events ingested. However, it is important to note that when you query for this metric, you should use a longSum aggregator. A count aggregator at query time will return the number of Druid rows for the time interval, which can be used to determine what the roll-up ratio was.

To clarify with an example, if you ingestion spec contains:

...
"metricsSpec" : [
      {
        "type" : "count",
        "name" : "count"
      },
...

You should query for the number of ingested rows with:

...
"aggregations": [
    { "type": "longSum", "name": "numIngestedEvents", "fieldName": "count" },
...

Schema-less dimensions

If the dimensions field is left empty in your ingestion spec, Druid will treat every column that is not the timestamp column, a dimension that has been excluded, or a metric column as a dimension. It should be noted that because of #658 these segments will be slightly larger than if the list of dimensions was explicitly specified in lexicographic order. This limitation does not impact query correctness- just storage requirements.

Including the same column as a dimension and a metric

One workflow with unique IDs is to be able to filter on a particular ID, while still being able to do fast unique counts on the ID column. If you are not using schema-less dimensions, this use case is supported by setting the name of the metric to something different than the dimension. If you are using schema-less dimensions, the best practice here is to include the same column twice, once as a dimension, and as a hyperUnique metric. This may involve some work at ETL time.

As an example, for schema-less dimensions, repeat the same column:

{"device_id_dim":123, "device_id_met":123}

and in your metricsSpec, include:

{ "type" : "hyperUnique", "name" : "devices", "fieldName" : "device_id_met" }

device_id_dim should automatically get picked up as a dimension.

4.3 KiB Raw Blame History