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

No meaningful error message upon failing ANALYZE .. PERSISTENT with some engines

    XMLWordPrintable

Details

    Description

      I can't imagine anyone would need statistics for OQGraph, but in general it would be good to produce a more meaningful error message. I suppose it may be the case not only for OQGraph.

      INSTALL SONAME 'ha_oqgraph';
       
      CREATE OR REPLACE TABLE oq_backing (
        origid INT UNSIGNED NOT NULL, 
        destid INT UNSIGNED NOT NULL,  
        PRIMARY KEY (origid, destid), 
        KEY (destid)
      );
       
      INSERT INTO oq_backing(origid, destid) 
       VALUES (1,2), (2,3), (3,4), (4,5), (2,6), (5,6);
       
      CREATE OR REPLACE TABLE t (
        latch VARCHAR(32) NULL,
        origid BIGINT UNSIGNED NULL,
        destid BIGINT UNSIGNED NULL,
        weight DOUBLE NULL,
        seq BIGINT UNSIGNED NULL,
        linkid BIGINT UNSIGNED NULL,
        KEY (latch, origid, destid) USING HASH,
        KEY (latch, destid, origid) USING HASH
      ) 
      ENGINE=OQGRAPH 
      data_table='oq_backing' origid='origid' destid='destid';
       
      ANALYZE TABLE t PERSISTENT FOR ALL;
      

      10.2 ceb40ef4

      MariaDB [test]> ANALYZE TABLE t PERSISTENT FOR ALL;
      +--------+---------+----------+------------------+
      | Table  | Op      | Msg_type | Msg_text         |
      +--------+---------+----------+------------------+
      | test.t | analyze | status   | Operation failed |
      +--------+---------+----------+------------------+
      1 row in set (0.002 sec)
      

      Attachments

        Activity

          People

            psergei Sergei Petrunia
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.