--- layout: doc_page --- # Lookups
Lookups are an experimental feature.
Lookups are a concept in Druid where dimension values are (optionally) replaced with new values. See [dimension specs](../querying/dimensionspecs.html) for more information. For the purpose of these documents, a "key" refers to a dimension value to match, and a "value" refers to its replacement. So if you wanted to rename `appid-12345` to `Super Mega Awesome App` then the key would be `appid-12345` and the value would be `Super Mega Awesome App`. It is worth noting that lookups support use cases where keys map to unique values (injective) such as a country code and a country name, and also supports use cases where multiple IDs map to the same value, e.g. multiple app-ids belonging to a single account manager. Lookups do not have history. They always use the current data. This means that if the chief account manager for a particular app-id changes, and you issue a query with a lookup to store the app-id to account manager relationship, it will return the current account manager for that app-id REGARDLESS of the time range over which you query. If you require data time range sensitive lookups, such a use case is not currently supported dynamically at query time, and such data belongs in the raw denormalized data for use in Druid. Very small lookups (count of keys on the order of a few dozen to a few hundred) can be passed at query time as a "map" lookup as per [dimension specs](../querying/dimensionspecs.html). Other lookup types are available as extensions, including: - Globally cached lookups from local files, remote URIs, or JDBC through [lookups-cached-global](../development/extensions-core/lookups-cached-global.html). - Globally cached lookups from a Kafka topic through [kafka-extraction-namespace](../development/extensions-core/kafka-extraction-namespace.html). Dynamic Configuration ---------------------
Dynamic lookup configuration is an experimental feature. Static configuration is no longer supported.
The following documents the behavior of the cluster-wide config which is accessible through the coordinator. The configuration is propagated through the concept of "tier" of servers. A "tier" is defined as a group of services which should receive a set of lookups. For example, you might have all historicals be part of `__default`, and Peons be part of individual tiers for the datasources they are tasked with. The tiers for lookups are completely independent of historical tiers. These configs are accessed using JSON through the following URI template ``` http://:/druid/coordinator/v1/lookups/{tier}/{id} ``` All URIs below are assumed to have `http://:` prepended. If you have NEVER configured lookups before, you MUST post an empty json object `{}` to `/druid/coordinator/v1/lookups` to initialize the configuration. These endpoints will return one of the following results: * 404 if the resource is not found * 400 if there is a problem in the formatting of the request * 202 if the request was accepted asynchronously (`POST` and `DELETE`) * 200 if the request succeeded (`GET` only) ## Configuration propagation behavior The configuration is propagated to the query serving nodes (broker / router / peon / historical) by the coordinator. The query serving nodes have an internal API for managing `POST`/`GET`/`DELETE` of lookups. The coordinator periodically checks the dynamic configuration for changes and, when it detects a change it does the following: 1. Post all lookups for a tier to all Druid nodes within that tier. 2. Delete lookups from a tier which were dropped between the prior configuration values and this one. If there is no configuration change, the coordinator checks for any nodes which might be new since the last time it propagated lookups and adds all lookups for that node (assuming that node's tier has lookups). If there are errors while trying to add or update configuration on a node, that node is temporarily skipped until the next management period. The next management period the update will attempt to be propagated again. If there is an error while trying to delete a lookup from a node (or if a node is down when the coordinator is propagating the config), the delete is not attempted again. In such a case it is possible that a node has lookups that are no longer managed by the coordinator. ## Bulk update Lookups can be updated in bulk by posting a JSON object to `/druid/coordinator/v1/lookups`. The format of the json object is as follows: ```json { "tierName": { "lookupExtractorFactoryName": { "type": "someExtractorFactoryType", "someExtractorField": "someExtractorValue" } } } ``` So a config might look something like: ```json { "__default": { "country_code": { "type": "map", "map": {"77483": "United States"} }, "site_id": { "type": "cachedNamespace", "extractionNamespace": { "type": "jdbc", "connectorConfig": { "createTables": true, "connectURI": "jdbc:mysql:\/\/localhost:3306\/druid", "user": "druid", "password": "diurd" }, "table": "lookupTable", "keyColumn": "country_id", "valueColumn": "country_name", "tsColumn": "timeColumn" }, "firstCacheTimeout": 120000, "injective":true }, "site_id_customer1": { "type": "map", "map": {"847632": "Internal Use Only"} }, "site_id_customer2": { "type": "map", "map": {"AHF77": "Home"} } }, "realtime_customer1": { "country_code": { "type": "map", "map": {"77483": "United States"} }, "site_id_customer1": { "type": "map", "map": {"847632": "Internal Use Only"} } }, "realtime_customer2": { "country_code": { "type": "map", "map": {"77483": "United States"} }, "site_id_customer2": { "type": "map", "map": {"AHF77": "Home"} } } } ``` All entries in the map will UPDATE existing entries. No entries will be deleted. ## Update Lookup A `POST` to a particular lookup extractor factory via `/druid/coordinator/v1/lookups/{tier}/{id}` will update that specific extractor factory. For example, a post to `/druid/coordinator/v1/lookups/realtime_customer1/site_id_customer1` might contain the following: ```json { "type": "map", "map": {"847632": "Internal Use Only"} } ``` This will replace the `site_id_customer1` lookup in the `realtime_customer1` with the definition above. ## Get Lookup A `GET` to a particular lookup extractor factory is accomplished via `/druid/coordinator/v1/lookups/{tier}/{id}` Using the prior example, a `GET` to `/druid/coordinator/v1/lookups/realtime_customer2/site_id_customer2` should return ```json { "type": "map", "map": {"AHF77": "Home"} } ``` ## Delete Lookup A `DELETE` to `/druid/coordinator/v1/lookups/{tier}/{id}` will remove that lookup from the cluster. ## List tier names A `GET` to `/druid/coordinator/v1/lookups` will return a list of known tier names in the dynamic configuration. To discover a list of tiers currently active in the cluster **instead of** ones known in the dynamic configuration, the parameter `discover=true` can be added as per `/druid/coordinator/v1/lookups?discover=true`. ## List lookup names A `GET` to `/druid/coordinator/v1/lookups/{tier}` will return a list of known lookup names for that tier. # Internal API The Peon, Router, Broker, and Historical nodes all have the ability to consume lookup configuration. There is an internal API these nodes use to list/load/drop their lookups starting at `/druid/listen/v1/lookups`. These follow the same convention for return values as the cluster wide dynamic configuration. Usage of these endpoints is quite advanced and not recommended for most users. The endpoints are as follows: ## Get Lookups A `GET` to the node at `/druid/listen/v1/lookups` will return a json map of all the lookups currently active on the node. The return value will be a json map of the lookups to their extractor factories. ```json { "some_lookup_name": { "type": "map", "map": {"77483": "United States"} } } ``` ## Get Lookup A `GET` to the node at `/druid/listen/v1/lookups/some_lookup_name` will return the LookupExtractorFactory for the lookup identified by `some_lookup_name`. The return value will be the json representation of the factory. ```json { "type": "map", "map": {"77483", "United States"} } ``` ## Bulk Add or Update Lookups A `POST` to the node at `/druid/listen/v1/lookups` of a JSON map of lookup names to LookupExtractorFactory will cause the service to add or update its lookups. The return value will be a JSON map in the following format: ```json { "status": "accepted", "failedUpdates": {} } ``` If a lookup cannot be started, or is left in an undefined state, the lookup in error will be returned in the `failedUpdates` field as per: ```json { "status": "accepted", "failedUpdates": { "country_code": { "type": "map", "map": {"77483": "United States"} } } } ``` The `failedUpdates` field of the return value should be checked if a user is wanting to assure that every update succeeded. ## Add or Update Lookup A `POST` to the node at `/druid/listen/v1/lookups/some_lookup_name` will behave very similarly to a bulk update. If `some_lookup_name` is desired to have the LookupExtractorFactory definition of ```json { "type": "map", "map": {"77483": "United States"} } ``` Then a post to `/druid/listen/v1/lookups/some_lookup_name` will behave the same as a `POST` to `/druid/listen/v1/lookups` of ```json { "some_lookup_name": { "type": "map", "map": {"77483": "United States"} } } ``` ## Remove a Lookup A `DELETE` to `/druid/listen/v1/lookups/some_lookup_name` will remove that lookup from the node. Success will reflect the ID. # Configuration See the [coordinator configuration guilde](../configuration/coordinator.html) for coordinator configuration To configure a Broker / Router / Historical / Peon to announce itself as part of a lookup tier, use the `druid.zk.paths.lookupTier` property. |Property | Description | Default | |---------|-------------|---------| |`druid.lookup.lookupTier`| The tier for **lookups** for this node. This is independent of other tiers.|`__default`| |`druid.lookup.lookupTierIsDatasource`|For some things like indexing service tasks, the datasource is passed in the runtime properties of a task. This option fetches the tierName from the same value as the datasource for the task. It is suggested to only use this as peon options for the indexing service, if at all. If true, `druid.lookup.lookupTier` MUST NOT be specified|`"false"`| To configure the behavior of the dynamic configuration manager, use the following properties on the coordinator: |Property|Description|Default| |--------|-----------|-------| |`druid.manager.lookups.hostDeleteTimeout`|Timeout (in ms) PER HOST for processing DELETE requests for dropping lookups|`1000`(1 second)| |`druid.manager.lookups.hostUpdateTimeout`|Timeout (in ms) PER HOST for processing an update/add (POST) for new or updated lookups|`10000`(10 seconds)| |`druid.manager.lookups.updateAllTimeout`|Timeout (in ms) TOTAL for processing update/adds on ALL hosts. Safety valve in case too many hosts timeout on their update|`60000`(1 minute)| |`druid.manager.lookups.period`|How long to pause between management cycles|`30000`(30 seconds)| |`druid.manager.lookups.threadPoolSize`|Number of service nodes that can be managed concurrently|`10`| ## Saving configuration across restarts It is possible to save the configuration across restarts such that a node will not have to wait for coordinator action to re-populate its lookups. To do this the following property is set: |Property|Description|Default| |--------|-----------|-------| |`druid.lookup.snapshotWorkingDir`| Working path used to store snapshot of current lookup configuration, leaving this property null will disable snapshot/bootstrap utility|null| ## Introspect a Lookup Lookup implementations can provide some introspection capabilities by implementing `LookupIntrospectHandler`. User will send request to `/druid/lookups/v1/introspect/{lookupId}` to enable introspection on a given lookup. For instance you can list all the keys/values of a map based lookup by issuing a `GET` request to `/druid/lookups/v1/introspect/{lookupId}/keys"` or `/druid/lookups/v1/introspect/{lookupId}/values"`