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

Error code miscommunication between Columnstore and server

Details

    • Bug
    • Status: Open (View Workflow)
    • Trivial
    • Resolution: Unresolved
    • None
    • Icebox
    • None
    • None

    Description

      10.7 8dd4794c4

      		 
      MariaDB [db]> create table t (a tinyint) engine=Columnstore;
      		 
      Query OK, 0 rows affected (1.355 sec)
      		 
       
      		 
      MariaDB [db]> insert into t values (1),(100);
      		 
      Query OK, 2 rows affected (0.650 sec)
      		 
      Records: 2  Duplicates: 0  Warnings: 0
      		 
       
      		 
      MariaDB [db]> update t set a = a*2;
      		 
      ERROR 1264 (22003): CAL0002: IDB-2025: Data truncated for column 'a' 
      MariaDB [db]> show warnings;
      		 
      +-------+------+---------------------------------------------------------------------+
      		 
      | Level | Code | Message                                                             |
      		 
      +-------+------+---------------------------------------------------------------------+
      		 
      | Error | 1264 | CAL0002: IDB-2025: Data truncated for column 'a'                    |
      		 
      | Error | 1030 | Got error 1815 "Unknown error 1815" from storage engine ColumnStore |
      		 
      +-------+------+---------------------------------------------------------------------+
      		 
      2 rows in set (0.000 sec)

      So, it appears that the initial error happens inside the Colunstore, but then it passed over as error 1815 ER_INTERNAL_ERROR and reported as "Unknown error". I have only found a couple of "Unknown error 1815" by a Google search, and they both belong to Columnstore, so maybe there is some room for improvement.

      Repeating the same exercise several times makes Columnstore/server to switch from reporting ER_WARN_DATA_OUT_OF_RANGE + ER_GET_ERRNO to direct ER_INTERNAL_ERROR. It seems to be happening non-deterministically, but frequently enough.

      drop table if exists t;
      		 
      create table t (a tinyint) engine=Columnstore;
      		 
      insert into t values (1),(100);
      		 
      insert into t select a*2 from t;
      		 
      insert into t values (1),(100);
      		 
      insert into t select a*2 from t;

      Result

      		 
      MariaDB [db]> create table t (a tinyint) engine=Columnstore;
      		 
      Query OK, 0 rows affected (1.542 sec)
      		 
       
      		 
      MariaDB [db]> insert into t values (1),(100);
      		 
      Query OK, 2 rows affected (0.625 sec)
      		 
      Records: 2  Duplicates: 0  Warnings: 0
      		 
       
      		 
      MariaDB [db]> insert into t select a*2 from t;
      		 
      ERROR 1264 (22003): Out of range value for column 'a' at row 1
      		 
      MariaDB [db]> insert into t values (1),(100);
      		 
      Query OK, 2 rows affected (0.600 sec)
      		 
      Records: 2  Duplicates: 0  Warnings: 0
      		 
       
      		 
      MariaDB [db]> insert into t select a*2 from t;
      		 
      ERROR 1815 (HY000): Internal error: Unknown error
      		 
      MariaDB [db]>

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26699 Row counter does not work consistently for Columnstore tables

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            Description {code:sql|title=10.7 8dd4794c4}
            Query OK, 0 rows affected (1.355 sec)

            MariaDB [db]> insert into t values (1),(100);
            Query OK, 2 rows affected (0.650 sec)
            Records: 2 Duplicates: 0 Warnings: 0

            MariaDB [db]> update t set a = a*2;
            ERROR 1264 (22003): CAL0002: IDB-2025: Data truncated for column 'a'
            MariaDB [db]> show warnings;
            +-------+------+---------------------------------------------------------------------+
            | Level | Code | Message |
            +-------+------+---------------------------------------------------------------------+
            | Error | 1264 | CAL0002: IDB-2025: Data truncated for column 'a' |
            | Error | 1030 | Got error 1815 "Unknown error 1815" from storage engine ColumnStore |
            +-------+------+---------------------------------------------------------------------+
            2 rows in set (0.000 sec)
            {code}

            So, it appears that the initial error happens inside the Colunstore, but then it passed over as error 1815 ER_INTERNAL_ERROR and reported as "Unknown error". I have only found a couple of "Unknown error 1815" by a Google search, and they both belong to Columnstore, so maybe there is some room for improvement.             		{code:sql|title=10.7 8dd4794c4}
            MariaDB [db]> create table t (a tinyint) engine=Columnstore;
            Query OK, 0 rows affected (1.355 sec)

            MariaDB [db]> insert into t values (1),(100);
            Query OK, 2 rows affected (0.650 sec)
            Records: 2 Duplicates: 0 Warnings: 0

            MariaDB [db]> update t set a = a*2;
            ERROR 1264 (22003): CAL0002: IDB-2025: Data truncated for column 'a'
            MariaDB [db]> show warnings;
            +-------+------+---------------------------------------------------------------------+
            | Level | Code | Message |
            +-------+------+---------------------------------------------------------------------+
            | Error | 1264 | CAL0002: IDB-2025: Data truncated for column 'a' |
            | Error | 1030 | Got error 1815 "Unknown error 1815" from storage engine ColumnStore |
            +-------+------+---------------------------------------------------------------------+
            2 rows in set (0.000 sec)
            {code}

            So, it appears that the initial error happens inside the Colunstore, but then it passed over as error 1815 ER_INTERNAL_ERROR and reported as "Unknown error". I have only found a couple of "Unknown error 1815" by a Google search, and they both belong to Columnstore, so maybe there is some room for improvement.
            elenst Elena Stepanova made changes -
            Description {code:sql|title=10.7 8dd4794c4}
            MariaDB [db]> create table t (a tinyint) engine=Columnstore;
            Query OK, 0 rows affected (1.355 sec)

            MariaDB [db]> insert into t values (1),(100);
            Query OK, 2 rows affected (0.650 sec)
            Records: 2 Duplicates: 0 Warnings: 0

            MariaDB [db]> update t set a = a*2;
            ERROR 1264 (22003): CAL0002: IDB-2025: Data truncated for column 'a'
            MariaDB [db]> show warnings;
            +-------+------+---------------------------------------------------------------------+
            | Level | Code | Message |
            +-------+------+---------------------------------------------------------------------+
            | Error | 1264 | CAL0002: IDB-2025: Data truncated for column 'a' |
            | Error | 1030 | Got error 1815 "Unknown error 1815" from storage engine ColumnStore |
            +-------+------+---------------------------------------------------------------------+
            2 rows in set (0.000 sec)
            {code}

            So, it appears that the initial error happens inside the Colunstore, but then it passed over as error 1815 ER_INTERNAL_ERROR and reported as "Unknown error". I have only found a couple of "Unknown error 1815" by a Google search, and they both belong to Columnstore, so maybe there is some room for improvement.             		{code:sql|title=10.7 8dd4794c4}
            MariaDB [db]> create table t (a tinyint) engine=Columnstore;
            Query OK, 0 rows affected (1.355 sec)

            MariaDB [db]> insert into t values (1),(100);
            Query OK, 2 rows affected (0.650 sec)
            Records: 2 Duplicates: 0 Warnings: 0

            MariaDB [db]> update t set a = a*2;
            ERROR 1264 (22003): CAL0002: IDB-2025: Data truncated for column 'a'
            MariaDB [db]> show warnings;
            +-------+------+---------------------------------------------------------------------+
            | Level | Code | Message |
            +-------+------+---------------------------------------------------------------------+
            | Error | 1264 | CAL0002: IDB-2025: Data truncated for column 'a' |
            | Error | 1030 | Got error 1815 "Unknown error 1815" from storage engine ColumnStore |
            +-------+------+---------------------------------------------------------------------+
            2 rows in set (0.000 sec)
            {code}

            So, it appears that the initial error happens inside the Colunstore, but then it passed over as error 1815 ER_INTERNAL_ERROR and reported as "Unknown error". I have only found a couple of "Unknown error 1815" by a Google search, and they both belong to Columnstore, so maybe there is some room for improvement.

            Repeating the same exercise several times makes Columnstore/server to switch from reporting ER_WARN_DATA_OUT_OF_RANGE + ER_GET_ERRNO to direct ER_INTERNAL_ERROR. It seems to be happening non-deterministically, but frequently enough.

            {code:sql}
            drop table if exists t;
            create table t (a tinyint) engine=Columnstore;
            insert into t values (1),(100);
            insert into t select a*2 from t;
            insert into t values (1),(100);
            insert into t select a*2 from t;
            {code}

            {code:sql|title=Result}
            MariaDB [db]> create table t (a tinyint) engine=Columnstore;
            Query OK, 0 rows affected (1.542 sec)

            MariaDB [db]> insert into t values (1),(100);
            Query OK, 2 rows affected (0.625 sec)
            Records: 2 Duplicates: 0 Warnings: 0

            MariaDB [db]> insert into t select a*2 from t;
            ERROR 1264 (22003): Out of range value for column 'a' at row 1
            MariaDB [db]> insert into t values (1),(100);
            Query OK, 2 rows affected (0.600 sec)
            Records: 2 Duplicates: 0 Warnings: 0

            MariaDB [db]> insert into t select a*2 from t;
            ERROR 1815 (HY000): Internal error: Unknown error
            MariaDB [db]>
            {code}
            elenst Elena Stepanova made changes -
            toddstoffel Todd Stoffel (Inactive) made changes -
            Rank Ranked lower
            toddstoffel Todd Stoffel (Inactive) made changes -
            Rank Ranked higher
            toddstoffel Todd Stoffel (Inactive) made changes -
            Rank Ranked lower
            toddstoffel Todd Stoffel (Inactive) made changes -
            Fix Version/s Icebox [ 22302 ]

            People

              Unassigned Unassigned
              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.