Actions
Feature #5223
openKB Recalc shouldn't require update-delete access to the KB-results cache
Start date:
08/25/2014
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
At the moment KB Recalc is implemented in the way when it calculates the KB-results cache in two steps:
- first it uses MySQL abilities to perform a quick matching that doesn't compare error traces,
- second it uses Perl scripts to compare error traces.
And due to these steps are independent it needs to either update or delete some records from the cache (e.g. if the quick matching was successful but error traces aren't the same).
Although it looks conceptually but it requires extra access rights and thus should be reimplemented.
No data to display
Actions