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

SELECT DISTINCT returns an incorrect number of rows when ORDER BY is used

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 23.10.2
    • None
    • PrimProc
    • None

    Description

      Consider the example:

      create table mcs1(i bigint, i2 bigint)engine=columnstore;
      insert into mcs1 values (1,2),(3,4),(3,5);
       
      select disctinct i from mcs1;
      MariaDB [test]> select distinct i from mcs1;
      +------+
      | i    |
      +------+
      |    1 |
      |    3 |
      +------+
      2 rows in set (0.080 sec)
       
      MariaDB [test]> select distinct i from mcs1 order by i2;
      +------+
      | i    |
      +------+
      |    1 |
      |    3 |
      |    3 |
      +------+
      3 rows in set (0.028 sec)
      

      Attachments

        Activity

          People

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