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

Can't delete saturated values

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 25.10.3
    • None
    • None
    • None

    Description

      We recently saw an issue where values from t1 (INT UNSIGNED) were copied to t2 (INT). This caused data saturation for values above 2147483647, as expected.

      The unexpected behavior came from trying to delete values that were subject to data saturation. A SELECT query showed the correct number of rows with the saturated value:

      SELECT COUNT(*) FROM t2 WHERE id=2147483647;
      +------------+
      | COUNT(*)   |
      +------------+
      | 2973342087 |
      +------------+
      

      But the DELETE statement couldn't find the same rows:

      DELETE FROM t2 WHERE id = 2147483647;
      Query OK, 0 rows affected (5.925 sec)
      

      We also tried explicitly casting `id` as SIGNED or UNSIGNED in the DELETE statement, but there was no effect. In the end, the table had to be rebuilt from scratch because the saturated values couldn't be removed. If there's a workaround for this issue, we couldn't find it in the Columnstore documentation.

      Attachments

        Activity

          People

            Unassigned Unassigned
            j_kyle J Kyle Turner
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.