Now, I aim to replace the location using an automatic lookup based on the ID "EF_97324_pewpew_sla." Unfortunately, I encounter an issue where I either retrieve only the location from the table, omi...
See more...
Now, I aim to replace the location using an automatic lookup based on the ID "EF_97324_pewpew_sla." Unfortunately, I encounter an issue where I either retrieve only the location from the table, omitting the rest, or I only receive the values extracted from the field extraction. I think you meant to say that your extraction populates location field with every id, even in those that do not contain location information. Instead of creating a table with all possible id's, you want to use a sparsely populated lookup to selectively override "bad" location value in those events with "bad" id's. Is this correct? Let me restate the requirement as this: if a lookup value exists, you want it to take precedence over any value your field extraction populates; if a lookup value does not exist, use the extracted value. SPL can use coalesce to signal precedence. You need to name extraction and lookup fields differently. Say, you name your extracted field location_may_be_bad, and the lookup output field just location, you can then use this to get the location | eval location = coalesce(location, location_may_be_bad) Hope this helps.