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

Post upgrade to 23.10.4, some of the queries giving different set of results upon executing multiple times.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 23.10.4
    • 23.02.16, 23.10.7, 25.10.0
    • None
    • None
    • 2025-8

    Description

      One of our customer reported after upgrading to MariaDB Columnstore 23.10.4 from 23.02.14, some of the SELECT queries specially the ones using the aggregation functions like count(), max(), min() etc.. upon running multiple times, giving different result set.

      It is also noted that after disabling AllowDiskBasedAggregation, they can see stable result set.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MCOL-6206 same query different results

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MCOL-6075 Research/Reproduce 23.10.4 Memory Allocation Related Errors

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              alexey.antipovsky Aleksei Antipovskii
              suresh.ramagiri@mariadb.com suresh ramagiri
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 10d
                  10d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 2d 1h Time Not Required
                  2d 1h

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.