Refresh a filter via a db update instead of clicking refresh filter cache?
Answered
I have a piece of master data that is common across hundreds of reports.
The list of valid values in the data has changed. It is taking too long to try to update each report by clicking refresh filter cache. Is there a way to do it at the database level instead?
If so can you please share the sql to do so
Thanks
The same question
Further to this, can i do a
update yfinadm.cachedfiltervalue set cachedvalue=<NEW VALUE> where cachedvalue=<OLD VALUE>;
Further to this, can i do a
update yfinadm.cachedfiltervalue set cachedvalue=<NEW VALUE> where cachedvalue=<OLD VALUE>;
Hi Angela,
yes that will work, and just be aware that you won't actually see the new cached filter values until you restart Yellowfin afterwards, that is because backend modifications don't automatically update the application's local cache (i.e. Yellowfin caches most of its metadata locally so it is quicker to retrieve than querying the database).
And I have to remind you because we always remind clients who are going to undertake backend modifications - make sure you back up your database immediately beforehand.
regards,
David
Hi Angela,
yes that will work, and just be aware that you won't actually see the new cached filter values until you restart Yellowfin afterwards, that is because backend modifications don't automatically update the application's local cache (i.e. Yellowfin caches most of its metadata locally so it is quicker to retrieve than querying the database).
And I have to remind you because we always remind clients who are going to undertake backend modifications - make sure you back up your database immediately beforehand.
regards,
David
Hi Angela,
just wondering whether you've had a chance yet to try this out, and if so, how did it go?
regards,
David
Hi Angela,
just wondering whether you've had a chance yet to try this out, and if so, how did it go?
regards,
David
Hi Angela,
just informing you of a new Knowledge Base article that may be of interest to you because it is about avoiding having to restart Yellowfin after making backend modifications to the Yellowfin database.
regards,
David
Hi Angela,
just informing you of a new Knowledge Base article that may be of interest to you because it is about avoiding having to restart Yellowfin after making backend modifications to the Yellowfin database.
regards,
David
Replies have been locked on this page!