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

No warning when filters are given as a comma-separated list instead of a pipe-separated list

    XMLWordPrintable

Details

    • MXS-SPRINT-282
    • Unexpected results
    • MaxScale now logs a better error when the wrong delimiter is used for a filter list.

    Description

      A lack of caffeine resulted in me using filters=filter1,filter2 in my configuration and the error was that the filter filter1,filter2 wasn't found. This is of course obvious once I realize I used the wrong delimiter but for someone who's not familiar, this isn't necessarily obvious.

      For comma-separated as well as space separated lists, MaxScale should log a helpful warning if the filter list looks valid but uses the wrong delimiter.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:

              Time Tracking

                Estimated:
                Original Estimate - 0.5d
                0.5d
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 0.5d
                0.5d

                Git Integration

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