[MXS-2336] Persisted configurations aren't backwards compatible Created: 2019-02-18 Updated: 2019-10-28 Resolved: 2019-10-28 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 2 |
| Labels: | None | ||
| Description |
|
The port parameter that has a default value of 3306 in 2.3 does not have a default value in 2.2 which prevents downgrades when persisted configurations have been created. This is caused by the conditional dumping code in dump_if_changed that only persists the change if it is different from the default value. This was intended as a way to allow new user-defined configuration parameters in the main configuration file but it also causes this problem. |
| Comments |
| Comment by markus makela [ 2019-10-28 ] |
|
As new parameters can be added in newer releases, making the runtime generated configurations backwards compatible isn't easy. The runtime changes should always be coalesced into a static configuration before a downgrade. |