Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-113

install_calpont_mysql.sh returns function not found errors on a new installation

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 1.0.2
    • Build
    • None

    Description

      Build tested:

      mscadmin> getsoft
      getsoftwareinfo Thu Jun 9 12:39:08 2016

      Name : mariadb-columnstore-platform Relocations: (not relocatable)
      Version : 1.0 Vendor: MariaDB Corporation Ab
      Release : 0 Build Date: Thu 09 Jun 2016 11:04:20 AM EDT
      Install Date: Thu 09 Jun 2016 12:00:38 PM EDT Build Host: srvbuilder
      Group : Applications Source RPM: mariadb-columnstore-1.0-0.src.rpm

      After a new installation, the /tmp/mysql_install.log on the UM1 contains the following errors:

      [root@columnStore ~]# cat /tmp/mysql_install.log
      ERROR 1305 (42000) at line 16: FUNCTION mysql.caldisablepartitions does not exist
      ERROR 1305 (42000) at line 17: FUNCTION mysql.calenablepartitions does not exist
      ERROR 1305 (42000) at line 18: FUNCTION mysql.caldroppartitions does not exist
      ERROR 1305 (42000) at line 19: FUNCTION mysql.calshowpartitions does not exist
      ERROR 1305 (42000) at line 20: FUNCTION mysql.caldroppartitionsbyvalue does not exist
      ERROR 1305 (42000) at line 21: FUNCTION mysql.caldisablepartitionsbyvalue does not exist
      ERROR 1305 (42000) at line 22: FUNCTION mysql.calenablepartitionsbyvalue does not exist
      ERROR 1305 (42000) at line 23: FUNCTION mysql.calshowpartitionsbyvalue does not exist

      in the ../mysql/install_calpont_mysql.sh script, there are commands to drop some Columnstore specific functions, which does not exist on a new installations:

      DROP FUNCTION caldisablepartitions;
      DROP FUNCTION calenablepartitions;
      DROP FUNCTION caldroppartitions;
      DROP FUNCTION calshowpartitions;
      DROP FUNCTION caldroppartitionsbyvalue;
      DROP FUNCTION caldisablepartitionsbyvalue;
      DROP FUNCTION calenablepartitionsbyvalue;
      DROP FUNCTION calshowpartitionsbyvalue;

      These statements caused the errors messages in the mysql_install.log file. We should add the "if exists" keywords to the statements so that a warning, instead of an error, would be returned.

      MariaDB [(none)]> use mysql
      Database changed
      MariaDB [mysql]> drop function daniel;
      ERROR 1305 (42000): FUNCTION mysql.daniel does not exist
      MariaDB [mysql]> drop function if exists daniel;
      Query OK, 0 rows affected, 1 warning (0.00 sec)

      MariaDB [mysql]> show warnings;
      -----------------------------------------------

      Level Code Message

      -----------------------------------------------

      Note 1305 FUNCTION mysql.daniel does not exist

      -----------------------------------------------
      1 row in set (0.00 sec)

      I also noticed that are 11 DELETEs, 8 DROP FUNCTIONs, and 29 CREATE FUNCTIONs. Should they all be 29? I think we just did not keep up the list as time goes by.

      Attachments

        Activity

          People

            hill David Hill (Inactive)
            dleeyh Daniel Lee (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.