The loader_schedule option today is global across all the loaders specified in a plugin instance. This prohibits a user from setting different cache refresh policies for different loaders (and effectively local tables). Implementing loader_schedule option for each loader separately would enable this finer grained tuning.
filter {
jdbc_static {
loaders => [
{
id => "remote-servers"
query => "select ip, descr from ref.local_ips order by ip"
local_table => "servers"
loader_schedule => "0 22 * * *"
},
{
id => "remote-users"
query => "select firstname, lastname, userid from ref.local_users order by userid"
local_table => "users"
}
]
...
I may be easier to implement multiple schedulers via Java. I have used http://www.quartz-scheduler.org/ in prior projects with good success. (it also knows how to parse a cron string)
The loader_schedule option today is global across all the loaders specified in a plugin instance. This prohibits a user from setting different cache refresh policies for different loaders (and effectively local tables). Implementing loader_schedule option for each loader separately would enable this finer grained tuning.