From 985640f103cbced6434123dfc239b57abf60350b Mon Sep 17 00:00:00 2001 From: Hellmar Becker Date: Mon, 16 May 2022 16:50:24 +0200 Subject: [PATCH] Clarify the use of the Lookup API (#12088) * Update lookups.md * Update docs/querying/lookups.md Co-authored-by: 317brian <53799971+317brian@users.noreply.github.com> * Update docs/querying/lookups.md Co-authored-by: Charles Smith Co-authored-by: 317brian <53799971+317brian@users.noreply.github.com> --- docs/querying/lookups.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/querying/lookups.md b/docs/querying/lookups.md index ede272f7930..9fe104b4adb 100644 --- a/docs/querying/lookups.md +++ b/docs/querying/lookups.md @@ -272,7 +272,7 @@ 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/config/{tier}/{id}` will update that specific extractor factory. +A `POST` to a particular lookup extractor factory via `/druid/coordinator/v1/lookups/config/{tier}/{id}` creates or updates that specific extractor factory. For example, a post to `/druid/coordinator/v1/lookups/config/realtime_customer1/site_id_customer1` might contain the following: @@ -290,6 +290,8 @@ For example, a post to `/druid/coordinator/v1/lookups/config/realtime_customer1/ This will replace the `site_id_customer1` lookup in the `realtime_customer1` with the definition above. +Assign a unique version identifier each time you update a lookup extractor factory. Otherwise the call will fail. + ### Get all lookups A `GET` to `/druid/coordinator/v1/lookups/config/all` will return all known lookup specs for all tiers.