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

Update CPRange max/min for extent doing DML

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0, 1.2
    • Fix Version/s: 6.1.1
    • Component/s: ?
    • Labels:
      None

      Description

      An extent is marked as invalid if DELETE, INSERT, UPDATE touches this extent. The extent has to be reread by SELECT to become valid again. If one bulk inserts in the invalid extent then min/max values aren't updated in the EM.
      One should read the data out after DML operations and before you bulk inserting data to make extents touched by DML valid again. To reduce number of extents to read one could set an impossible filter to eliminate all valid extents.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              sergey.zefirov Sergey Zefirov
              Reporter:
              Richard Richard Stracke
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration