Red Hat Bugzilla – Bug 797356
MySQL plugin discovery of tables should be manually disabled
Last modified: 2013-09-01 06:03:46 EDT
Description of problem:
The MySQL plugin 'discovers' the list of tables and creates resources for each one. For my application, we create new hundreds of new database tables constantly which are soon dropped.
Is there a potential problem with adding these tables to the discovery queue? Should I attempt to patch the plugin to ignore these tables entirely?
If there's no issue, then perhaps I do not need to address this at all.
Actually, I'd rather prefer it if discovery was disabled (or could be) on a server or host basis. Is there such a way? Thanks.
Version-Release number of selected component (if applicable):
4.1, 4.2, etc.
** Note: I have a pending patch to disable this. As well as test the plugin for functionality.
triage 2/27/2012 mfoley, asantos, crouch, loleary
Created attachment 570671 [details]
Patch against 2f315f3f61a76e
Added change as well as unit test.
Again, has the same unit test code as 796983; but could be made to share this code or use Arquillian I suppose.
I think this looks like a good addition.
One question: you add the new plugin-config property "tableDiscovery" and if
this is not true, the discovery of tables is turned off.
Wouldn't that impact users that have the plugin already deployed ?
Thank you Elias !
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.