Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4184

No-op modifications to file paths do not cause the file to be re-read

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.4.0
    • Fix Version/s: 22.08.0
    • Component/s: REST-API
    • Labels:
      None

      Description

      If a modification to a path parameter doesn't change the value but the contents have changed, an attempt to modify it to the current value does not cause it to be re-read. This makes it hard to force MaxScale to re-read a file from disk and it has to be worked around by renaming the file or by moving it elsewhere.

      Treating all configuration modifications, even ones that do not change the actual values, as request to reapply any side-effects that might take place should fix this.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.