The logging settings will be saved with lower 'priority' than
any user settings. This will ensure the user settings
(if present) always override the global value.
Once the deprecated options go away we can again apply
the logging settings at the system level.
Reviewed: https:/ /review. openstack. org/311237 /git.openstack. org/cgit/ openstack/ trove/commit/ ?id=665bdaefc13 f3e91a3db557d61 5b4b96eed3b47c
Committed: https:/
Submitter: Jenkins
Branch: master
commit 665bdaefc13f3e9 1a3db557d615b4b 96eed3b47c
Author: Petr Malik <email address hidden>
Date: Fri Apr 29 15:34:51 2016 -0400
Deprecate 'guest_ log_long_ query_time'
Slow query time should be configurable on per-instance basis
via the existing configuration group mechanism (see the bug).
We need to deprecate the existing global conf property first.
The property has been deprecated on all datastores.
Validation rules have been updated on those that
support log retrieval as well:
- MySQL: long_query_time duration_ statement
- Percona: long_query_time
- Percona XtraDB Cluster: long_query_time
- PostgreSQL: log_min_
- MariaDB: long_query_time
The logging settings will be saved with lower 'priority' than
any user settings. This will ensure the user settings
(if present) always override the global value.
Once the deprecated options go away we can again apply
the logging settings at the system level.
Change-Id: I9c28ceb933b681 9b8e96556584b2e 26cab2155fb
DocImpact: Document deprecated properties
Partial-Bug: 1542485