Dictionary Key and Fields 

The <structure> clause describes the dictionary key and fields available for queries.

XML description:

<dictionary>
    <structure>
        <id>
            <name>Id</name>
        </id>

        <attribute>
            <!-- Attribute parameters -->
        </attribute>

        ...

    </structure>
</dictionary>

Attributes are described in the elements:

DDL query:

CREATE DICTIONARY dict_name (
    Id UInt64,
    -- attributes
)
PRIMARY KEY Id
...

Attributes are described in the query body:

  • PRIMARY KEYKey column
  • AttrName AttrTypeData column. There can be a multiple number of attributes.

Key 

ClickHouse supports the following types of keys:

  • Numeric key. UInt64. Defined in the <id> tag or using PRIMARY KEY keyword.
  • Composite key. Set of values of different types. Defined in the tag <key> or PRIMARY KEY keyword.

An xml structure can contain either <id> or <key>. DDL-query must contain single PRIMARY KEY.

Numeric Key 

Type: UInt64.

Configuration example:

<id>
    <name>Id</name>
</id>

Configuration fields:

  • name – The name of the column with keys.

For DDL-query:

CREATE DICTIONARY (
    Id UInt64,
    ...
)
PRIMARY KEY Id
...
  • PRIMARY KEY – The name of the column with keys.

Composite Key 

The key can be a tuple from any types of fields. The layout in this case must be complex_key_hashed or complex_key_cache.

The key structure is set in the element <key>. Key fields are specified in the same format as the dictionary attributes. Example:

<structure>
    <key>
        <attribute>
            <name>field1</name>
            <type>String</type>
        </attribute>
        <attribute>
            <name>field2</name>
            <type>UInt32</type>
        </attribute>
        ...
    </key>
...

or

CREATE DICTIONARY (
    field1 String,
    field2 String
    ...
)
PRIMARY KEY field1, field2
...

For a query to the dictGet* function, a tuple is passed as the key. Example: dictGetString('dict_name', 'attr_name', tuple('string for field1', num_for_field2)).

Attributes 

Configuration example:

<structure>
    ...
    <attribute>
        <name>Name</name>
        <type>ClickHouseDataType</type>
        <null_value></null_value>
        <expression>rand64()</expression>
        <hierarchical>true</hierarchical>
        <injective>true</injective>
        <is_object_id>true</is_object_id>
    </attribute>
</structure>

or

CREATE DICTIONARY somename (
    Name ClickHouseDataType DEFAULT '' EXPRESSION rand64() HIERARCHICAL INJECTIVE IS_OBJECT_ID
)

Configuration fields:

TagDescriptionRequired
nameColumn name.Yes
typeClickHouse data type.
ClickHouse tries to cast value from dictionary to the specified data type. For example, for MySQL, the field might be TEXT, VARCHAR, or BLOB in the MySQL source table, but it can be uploaded as String in ClickHouse.
Nullable is not supported.
Yes
null_valueDefault value for a non-existing element.
In the example, it is an empty string. You cannot use NULL in this field.
Yes
expressionExpression that ClickHouse executes on the value.
The expression can be a column name in the remote SQL database. Thus, you can use it to create an alias for the remote column.

Default value: no expression.
No
hierarchicalIf true, the attribute contains the value of a parent key for the current key. See Hierarchical Dictionaries.

Default value: false.
No
injectiveFlag that shows whether the id -> attribute image is injective.
If true, ClickHouse can automatically place after the GROUP BY clause the requests to dictionaries with injection. Usually it significantly reduces the amount of such requests.

Default value: false.
No
is_object_idFlag that shows whether the query is executed for a MongoDB document by ObjectID.

Default value: false.
No

See Also 

Rating: 1 - 1 votes

Was this content helpful?
★☆☆☆☆