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

Unable to configure nested parameters via MaxCtrl

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 6.1.4
    • 6.2.0
    • maxctrl
    • None

    Description

      MaxCtrl wrongly interprets nosqlprotocol.user my_user as the following JSON:

      { "nosqlprotocol.user": "my_user" }
      

      it should interpret it as a nested type:

      { "nosqlprotocol": { "user": "my_user" } }
      

      The inability to modify nosqlprotocol parameters is a separate problem tracked in MXS-3883.

      Original description:


      Our KB explains that the NoSQL listener must have certain protocol-speicific parameters explicitly configured -for example, username and password for the backend that will be used by all connections, coming to this listener:

      https://mariadb.com/kb/en/mariadb-maxscale-6-nosql-protocol-module/#parameters

      This works for static configuration, but not for dynamic one via maxctrl:

      [root@s4name assen.totin]# maxctrl alter listener mcs_mongo  nosqlprotocol.user mongo_test
      Error: Server at http://127.0.0.1:8989 responded with 403 Forbidden to `PATCH listeners/mcs_mongo`
      {
          "errors": [
              {
                  "detail": "listener: The parameter 'nosqlprotocol.user' is unrecognized."
              }
          ]
      }
      

      The listener itself before patching:

      [root@s4name assen.totin]# maxctrl show listeners
      ┌────────────┬───────────────────────────────────────────┐
      │ Name       │ mcs_mongo                                 │
      ├────────────┼───────────────────────────────────────────┤
      │ Service    │ mcs_service                               │
      ├────────────┼───────────────────────────────────────────┤
      │ Parameters │ {                                         │
      │            │     "address": "::",                      │
      │            │     "authenticator": null,                │
      │            │     "authenticator_options": null,        │
      │            │     "connection_init_sql_file": null,     │
      │            │     "port": 27017,                        │
      │            │     "protocol": "nosqlprotocol",          │
      │            │     "service": "mcs_service",             │
      │            │     "socket": null,                       │
      │            │     "sql_mode": "default",                │
      │            │     "ssl": false,                         │
      │            │     "ssl_ca_cert": null,                  │
      │            │     "ssl_cert": null,                     │
      │            │     "ssl_cert_verify_depth": 9,           │
      │            │     "ssl_cipher": null,                   │
      │            │     "ssl_crl": null,                      │
      │            │     "ssl_key": null,                      │
      │            │     "ssl_verify_peer_certificate": false, │
      │            │     "ssl_verify_peer_host": false,        │
      │            │     "ssl_version": "MAX",                 │
      │            │     "type": "listener"                    │
      │            │ }                                         │
      └────────────┴───────────────────────────────────────────┘
      

      MaxScale version:

      [root@s4name assen.totin]# rpm -q maxscale
      maxscale-6.1.4-1.rhel.7.x86_64
      

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              assen.totin Assen Totin (Inactive)
              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.