Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-30579

Confusing WSREP warning on HANDLER READ FIRST for spider table (possibly caused by zero-length self-referencing)

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL)
    • 10.5, 10.6, 10.11
    • Storage Engine - Spider
    • None

    Description

      Splitted from Item 7 of MDEV-29583.

      Attachments

        Issue Links

          split from

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29583 Disallow Spider self/dual/multi/cross-referencing tables, consider not executing/skipping/disabling init_connect for Spider user

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            ycp Yuchen Pei created issue -
            Roel Roel Van de Paar made changes -
            Field Original Value New Value
            serg Sergei Golubchik made changes -
            Fix Version/s 10.7 [ 24805 ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 10.8 [ 26121 ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 10.9 [ 26905 ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 10.10 [ 27530 ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 11.0 [ 28320 ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 10.4 [ 22408 ]

            People

              ycp Yuchen Pei
              ycp Yuchen Pei
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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