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

Missing match setting in filter(s) results in no match at all

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.6
    • Fix Version/s: 2.5.7
    • Component/s: Filter
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-122

      Description

      Documentation at the below link clearly says that "If match is not defined, all queries are considered to match.". All filter modules link to this place from their own pages.

      https://mariadb.com/kb/en/mariadb-maxscale-25-mariadb-maxscale-configuration-guide/#standard-regular-expression-settings-for-filters

      This is completely wrong, at least for Tee and QLA filters, likely for many (all?) others too. If no match clause is given in the filter's config section, the filter will NEVER match. It order to match all queries, one must specify:

      match=/.*/

      Unsure if this is a regression or not and if the MaxScale or the docs have to be fixed, but they MUST be aligned. Otherwise we just seem lame and cause confusion and frustration with customers.

        Attachments

          Activity

            People

            Assignee:
            esa.korhonen Esa Korhonen
            Reporter:
            assen.totin Assen Totin
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.