Not working: Lookup_set_value function

Does anyone have an example of some of the new lookup table functions?

rule "wireless ip to username"
  has_field("source_ip") &&
  has_field("username") &&
  to_string($message.state) == "success" &&
  cidr_match("", to_ip($message.source_ip))
lookup_set_value("username-lookup-table", to_string($message.source_ip), to_string($message.username));
//set_field("correlateduser", to_string($message.username));

I’ve been playing with this and things are not working as I would expect. The table/lookup cache does not seem to be updated when I go check manually.

I have built out an entirely new lookup table / cache / adapter with the following sample data:


I validated the lookups work as expected from both cache and lookup table tests.
I am attempting to test this in a pipeline:

let newValue = lookup_set_value("newtable", to_string("greg"), to_string("YELLOW"));
set_field("correlateduser", to_string(newValue));

Neither the new string “YELLOW” seems to be set, and the field “correlateduser” is not being updated. If I change the value for set_field, it is written properly as arbitrary value.

Doing the following results in “green” in my correlateduser field, so I at least know the rule is firing and the lookup works properly. Seems just setting values isn’t working? I’ve tried mixing in to_string as well.

let newValue = lookup_set_value("newtable", "greg", "YELLOW");
set_field("correlateduser", to_string(lookup_value("newtable", "greg", "notfound")));

he @gimmic

did you use that with a database based lookup table or did you try that with a csv based one?

@jan This has been with a CSV based list. Is that incompatible?

I’ve been confused as to why there isn’t an entirely “memory resident” adapter option, if we’re able to populate the cache from pipeline rule results?

he @gimmic
I have added some more information to the documentation. That was indeed missing - that you can modify only the database based lookup table…

sorry for that confusion.

Thanks, I’ll work on getting that implemented and tested. Appreciate the follow up.

I did not realize the mongodb data adapter was enterprise only. That’s garbage.
The entire function should be listed as an enterprise only function.


the current only Lookup table that can be used by this function is the MongoDB Lookup Table. BUT if someone else implement other lookup tables that has the ability to accept writes the same pipeline functions can be used. That is the reason marking this functions not as enterprise.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.