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

Report expected default version String

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 6.1.1
    • N/A
    • Core
    • None
    • MXS-SPRINT-214

    Description

      It occurs that maxscale default to version 10.4.32 by default (https://github.com/mariadb-corporation/MaxScale/blob/214b4e92737811ee21911acf7eb111ca84f6d4a0/server/modules/protocol/MariaDB/mariadb_client.cc#L91 )

      The problem is that some connectors rely on server version for some capabilities.
      When dealing with xpand, with version like 5.0.45-Xpand-5.3.16, having this default to 10.4 is problematic.

      For example when using java connector and query timeout, connector will then use `SET STATEMENT max_statement_time=xx FOR ` prefix for command thinking that server version is 10.1.2+, while it's not supported by server.

      A better solution is for maxscale to retain last connected server version in place of using that default version.

      Attachments

        Activity

          People

            markus makela markus makela
            diego dupin Diego Dupin
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.