Syntax special considerations - → This must be the name of lookup that contains the data you want to use to enrich your data.
Status |
---|
colour | Purple |
---|
title | "lookup_field" |
---|
| → This must be the lookup field you want to use to enrich your data, which must not be the same as the lookup key field.- → This must be the table field that will be used to find matches with the lookup key. The name can be different than the lookup key field as long as the data type coincide and the values it contains are potential matches (username-user). The absence of matches will return null and a different data type will return an error when running the query .
Status |
---|
colour | Green |
---|
title | timestamp_field |
---|
| → This must be the table timestamp that will be used to correlate with the lookup timestamp. A data type other than timestamp will return an error when running the query.
One-field lookups If your lookup is composed only of the key field because you are interested only in the correlation but not the enrichment, you need to use the operation Lookup (hlurjson). As an alternative, you can use lookups with two fields; the key field and a field with default values such as true. You can use the Lookup (lu) operation to enrich your data with the default values that indicate only correlation. |