Project: Druid (App Definition and Development / Database)
File: lookups-cached-global.md

id: lookups-cached-global title: "Globally Cached Lookups" <!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you under the Apache License, Version 2.0 (the ~ "License"); you may not use this file except in compliance ~ with the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, ~ software distributed under the License is distributed on an ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~ KIND, either express or implied. See the License for the ~ specific language governing permissions and limitations ~ under the License. --> To use this Apache Druid extension, `druid-lookups-cached-global` in the extensions load list. :::info Static configuration is no longer supported. Lookups can be configured through . ::: Globally cached lookups are appropriate for lookups which are not possible to pass at query time due to their size, or are not desired to be passed at query time because the data is to reside in and be handled by the Druid servers, and are small enough to reasonably populate in-memory. This usually means tens to tens of thousands of entries per lookup. Globally cached lookups all draw from the same cache pool, allowing each process to have a fixed cache pool that can be used by cached lookups. Globally cached lookups can be specified as part of the as a type of `cachedNamespace` ```json { "type": "cachedNamespace", "extractionNamespace": { "type": "uri", "uri": "file:/tmp/prefix/", "namespaceParseSpec": { "format": "csv", "columns": [ "[\"key\"", "\"value\"]" ] }, "pollPeriod": "PT5M" }, "firstCacheTimeout": 0 } ``` ```json { "type": "cachedNamespace", "extractionNamespace": { "type": "jdbc", "connectorConfig": { "connectURI": "jdbc:mysql:\/\/localhost:3306\/druid", "user": "druid", "password": "diurd" }, "table": "lookupTable", "keyColumn": "mykeyColumn", "valueColumn": "myValueColumn", "filter" : "myFilterSQL (Where clause statement e.g LOOKUPTYPE=1)", "tsColumn": "timeColumn" }, "firstCacheTimeout": 120000, "injective":true } ``` The parameters are as follows |Property|Description|Required|Default| |--|--|--|-| |`extractionNamespace`|Specifies how to populate the local cache. See below|Yes|-| |`firstCacheTimeout`|How long to wait (in ms) for the first run of the cache to populate. 0 indicates to not wait|No|`0` (do not wait)| |`injective`|If the underlying map is (keys and values are unique) then optimizations can occur internally by setting this to `true`|No|`false`| If `firstCacheTimeout` is set to a non-zero value, it should be less than `druid.manager.lookups.hostUpdateTimeout`. If `firstCacheTimeout` is NOT set, then management is essentially asynchronous and does not know if a lookup succeeded or failed in starting. In such a case logs from the processes using lookups should be monitored for repeated

Proper functionality of globally cached lookups requires the following extension to be loaded on the Broker, Peon, and Historical processes: `druid-lookups-cached-global` In a simple case where only one exists (`realtimecustomer2`) with one `cachedNamespace` lookup called `countrycode`, the resulting configuration JSON looks similar to the following: ```json { "realtime_customer2": { "country_code": { "version": "v0", "lookupExtractorFactory": { "type": "cachedNamespace", "extractionNamespace": { "type": "jdbc", "connectorConfig": { "connectURI": "jdbc:mysql:\/\/localhost:3306\/druid", "user": "druid", "password": "diurd" }, "table": "lookupValues", "keyColumn": "value_id", "valueColumn": "value_text", "filter": "value_type='country'", "tsColumn": "timeColumn" }, "firstCacheTimeout": 120000, "injective": true } } } } ``` Where the Coordinator endpoint `/druid/coordinator/v1/lookups/realtimecustomer2/countrycode` should return ```json { "version": "v0", "lookupExtractorFactory": { "type": "cachedNamespace", "extractionNamespace": { "type": "jdbc", "connectorConfig": { "connectURI": "jdbc:mysql://localhost:3306/druid", "user": "druid", "password": "diurd" }, "table": "lookupValues", "keyColumn": "value_id", "valueColumn": "value_text", "filter": "value_type='country'", "tsColumn": "timeColumn" }, "firstCacheTimeout": 120000, "injective": true } } ``` Lookups are cached locally on Historical processes. The following are settings used by the processes which service queries when setting namespaces (Broker, Peon, Historical) |Property|Description|Default| |--|--|-| |`druid.lookup.namespace.cache.type`|Specifies the type of caching to be used by the namespaces. May be one of [`offHeap`, `onHeap`]. `offHeap` uses a temporary file for off-heap storage of the namespace (memory mapped files). `onHeap` stores all cache on the heap in standard java map types.|`onHeap`| |`druid.lookup.namespace.numExtractionThreads`|The number of threads in the thread pool dedicated for lookup extraction and updates. This number may need to be scaled up, if you have a lot of lookups and they take long time to extract, to avoid timeouts.|2| |`druid.lookup.namespace.numBufferedEntries`|If using off-heap caching, the number of records to be stored on an on-heap buffer.|100,000| The cache is populated in different ways depending on the settings below. In general, most namespaces employ a `pollPeriod` at the end of which time they poll the remote resource of interest for updates. `onHeap` uses `ConcurrentMap`s in the java heap, and thus affects garbage collection and heap sizing. `offHeap` uses an on-heap buffer and MapDB using memory-mapped files in the java temporary directory. So if total number of entries in the `cachedNamespace` is in excess of the buffer's configured capacity, the extra will be kept in memory as page cache, and paged in and out by general OS tunings. It's highly recommended that `druid.lookup.namespace.numBufferedEntries` is set when using `offHeap`, the value should be chosen from the range between 10% and 50% of the number of entries in the lookup. For additional lookups, please see our . The remapping values for each globally cached lookup can be specified by a JSON object as per the following examples: ```json { "type":"uri", "uri": "s3://bucket/some/key/prefix/renames-0003.gz", "namespaceParseSpec":{ "format":"csv", "columns":[ "[\"key\"", "\"value\"]" ] }, "pollPeriod":"PT5M" } ``` ```json { "type":"uri", "uriPrefix": "s3://bucket/some/key/prefix/", "fileRegex":"renames-[0-9]*\\.gz", "namespaceParseSpec":{ "format":"csv", "columns":[ "[\"key\"", "\"value\"]" ] }, "pollPeriod":"PT5M", "maxHeapPercentage": 10 } ``` |Property|Description|Required|Default| |--|--|--|-| |`pollPeriod`|Period between polling for updates|No|0 (only once)| |`uri`|URI for the lookup file. Can be a file, HDFS, S3 or GCS path|Either `uri` or `uriPrefix` must be set|None| |`uriPrefix`|A URI prefix that specifies a directory or other searchable resource where lookup files are located |Either `uri` or `uriPrefix` must be set|None| |`fileRegex`|Optional regex for matching the file name under `uriPrefix`. Only used if `uriPrefix` is used|No|`".*"`| |`namespaceParseSpec`|How to interpret the data at the URI|Yes|| |`maxHeapPercentage`|The maximum percentage of heap size that the lookup should consume. If the lookup grows beyond this size, warning messages will be logged in the respective service

of JVM heap size| One of either `uri` or `uriPrefix` must be specified, as either a local file system (file://), HDFS (hdfs://), S3 (s3://) or GCS (gs://) location. HTTP location is not currently supported. The `pollPeriod` value specifies the period in ISO 8601 format between checks for replacement data for the lookup. If the source of the lookup is capable of providing a timestamp, the lookup will only be updated if it has changed since the prior tick of `pollPeriod`. A value of 0, an absent parameter, or `null` all mean populate once and do not attempt to look for new data later. Whenever an poll occurs, the updating system will look for a file with the most recent timestamp and assume that one with the most recent data set, replacing the local cache of the lookup data. The `namespaceParseSpec` can be one of a number of values. Each of the examples below would rename foo to bar, baz to bat, and buck to truck. All parseSpec types assumes each input is delimited by a new line. See below for the types of parseSpec supported. Only ONE file which matches the search will be used. For most implementations, the discriminator for choosing the URIs is by whichever one reports the most recent timestamp for its modification time. |Parameter|Description|Required|Default| ||--|--|-| |`columns`|The list of columns in the csv file|no if `hasHeaderRow` is set|`null`| |`keyColumn`|The name of the column containing the key|no|The first column| |`valueColumn`|The name of the column containing the value|no|The second column| |`hasHeaderRow`|A flag to indicate that column information can be extracted from the input files' header row|no|false| |`skipHeaderRows`|Number of header rows to be skipped|no|0| If both `skipHeaderRows` and `hasHeaderRow` options are set, `skipHeaderRows` is first applied. For example, if you set `skipHeaderRows` to 2 and `hasHeaderRow` to true, Druid will skip the first two lines and then extract column information from the third line. example input ``` bar,something,foo bat,something2,baz truck,something3,buck ``` example namespaceParseSpec ```json "namespaceParseSpec": { "format": "csv", "columns": ["value","somethingElse","key"], "keyColumn": "key", "valueColumn": "value" } ``` |Parameter|Description|Required|Default| ||--|--|-| |`columns`|The list of columns in the tsv file|yes|`null`| |`keyColumn`|The name of the column containing the key|no|The first column| |`valueColumn`|The name of the column containing the value|no|The second column| |`delimiter`|The delimiter in the file|no|tab (`\t`)| |`listDelimiter`|The list delimiter in the file|no| (`\u0001`)| |`hasHeaderRow`|A flag to indicate that column information can be extracted from the input files' header row|no|false| |`skipHeaderRows`|Number of header rows to be skipped|no|0| If both `skipHeaderRows` and `hasHeaderRow` options are set, `skipHeaderRows` is first applied. For example, if you set `skipHeaderRows` to 2 and `hasHeaderRow` to true, Druid will skip the first two lines and then extract column information from the third

example input ``` bar|something,1|foo bat|something,2|baz truck|something,3|buck ``` example namespaceParseSpec ```json "namespaceParseSpec": { "format": "tsv", "columns": ["value","somethingElse","key"], "keyColumn": "key", "valueColumn": "value", "delimiter": "|" } ``` |Parameter|Description|Required|Default| ||--|--|-| |`keyFieldName`|The field name of the key|yes|null| |`valueFieldName`|The field name of the value|yes|null| example input ```json {"key": "foo", "value": "bar", "somethingElse" : "something"} {"key": "baz", "value": "bat", "somethingElse" : "something"} {"key": "buck", "somethingElse": "something", "value": "truck"} ``` example namespaceParseSpec ```json "namespaceParseSpec": { "format": "customJson", "keyFieldName": "key", "valueFieldName": "value" } ``` With customJson parsing, if the value field for a particular row is missing or null then that line will be skipped, and will not be included in the lookup. The `simpleJson` lookupParseSpec does not take any parameters. It is simply a line delimited JSON file where the field is the key, and the field's value is the value. example input ```json {"foo": "bar"} {"baz": "bat"} {"buck": "truck"} ``` example namespaceParseSpec ```json "namespaceParseSpec":{ "format": "simpleJson" } ``` The JDBC lookups will poll a database to populate its local cache. If the `tsColumn` is set it must be able to accept comparisons in the format `'2015-01-01 00:00:00'`. For example, the following must be valid SQL for the table `SELECT FROM some_lookup_table WHERE timestamp_column > '2015-01-01 00:00:00'`. If `tsColumn` is set, the caching service will attempt to only poll values that were written after* the last sync. If `tsColumn` is not set, the entire table is pulled every time. |Parameter|Description|Required|Default| ||--|--|-| |`connectorConfig`|The connector config to use. You can set `connectURI`, `user` and `password`. You can selectively allow JDBC properties in `connectURI`. See for more details.|Yes|| |`table`|The table which contains the key value pairs|Yes|| |`keyColumn`|The column in `table` which contains the keys|Yes|| |`valueColumn`|The column in `table` which contains the values|Yes|| |`filter`|The filter to use when selecting lookups, this is used to create a where clause on lookup population|No|No Filter| |`tsColumn`| The column in `table` which contains when the key was updated|No|Not used| |`pollPeriod`|How often to poll the DB|No|0 (only once)| |`jitterSeconds`| How much jitter to add (in seconds) up to maximum as a delay (actual value will be used as random from 0 to `jitterSeconds`), used to distribute db load more evenly|No|0| |`loadTimeoutSeconds`| How much time (in seconds) it can take to query and populate lookup values. It will be helpful in lookup updates. On lookup update, it will wait maximum of `loadTimeoutSeconds` for new lookup to come up and continue serving from old lookup until new lookup successfully loads. |No|0| |`maxHeapPercentage`|The maximum percentage of heap size that the lookup should consume. If the lookup grows beyond this size, warning messages will be logged in the respective service logs.|No|10% of JVM heap size| ```json { "type":"jdbc", "connectorConfig":{ "connectURI":"jdbc:mysql://localhost:3306/druid", "user":"druid", "password":"diurd" }, "table":"somelookuptable", "keyColumn":"theolddim_value", "valueColumn":"thenewdim_value", "tsColumn":"timestamp_column", "pollPeriod":600000, "jitterSeconds": 120, "maxHeapPercentage": 10 } ``` :::info If using JDBC, you will need to add your database's client JAR files to the extension's directory. For Postgres, the connector JAR is already included. See the MySQL extension documentation for instructions to obtain or connector libraries. The connector JAR should reside in the classpath of Druid's main class loader. To add the connector JAR to the classpath, you can copy the downloaded file to `lib/` under the distribution root directory. Alternatively, create a symbolic link to the connector in the `lib` directory. ::: Globally cached lookups have introspection points at `/keys` and `/values` which return a complete set of the keys and values (respectively) in the lookup. Introspection to `/` returns the entire map. Introspection to `/version` returns the version indicator for the lookup.