[MXS-3594] Filters can be altered but no filter declares parameters as alterable Created: 2021-06-04  Updated: 2021-08-02  Resolved: 2021-08-02

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 6.0.0
Fix Version/s: 6.2.0

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MXS-3683 Make filter parameter table editable ... Closed
PartOf
includes MXS-2754 Add filter alteration Closed
includes MXS-3708 Make cache filter modifiable at runtime Closed
includes MXS-3709 Masking filter cannot be modified at ... Closed
includes MXS-3710 Namedserverfilter cannot be modified ... Closed
includes MXS-3711 Qlafilter cannot be modified at runtime Closed
Sprint: MXS-SPRINT-136

 Description   

6.0.0 adds the filter alteration mechanism but the filters still declare their parameters as modifiable only on startup. This effectively makes the filter alteration useless until the parameter declarations are modified. For most filters this should be a relatively straightforward process of changing the flag from AT_STARTUP to AT_RUNTIME and changing from native parameter types to the configuration types that are thread-safe.



 Comments   
Comment by markus makela [ 2021-07-31 ]

Current modifications make all filters alterable at runtime except the following:

  • dbfwfilter
  • cache
  • masking
  • namedserverfilter
  • qlafilter
  • luafilter
  • tpmfilter
Generated at Thu Feb 08 04:22:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.