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

Regression in 1.4 working_ssb_compareLogOnly/sub/order_limit_sub

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.4.1
    • Fix Version/s: 1.4.3
    • Component/s: Connector, ExeMgr
    • Labels:
      None
    • Sprint:
      2020-2

      Description

      working_ssb_compareLogOnly/sub/order_limit_sub, the second query gives the wrong answer:

      select * from
      (select lo_orderkey, count
      from lineorder where lo_orderkey in
      (select *
      from (select lo_orderkey
      from lineorder
      join dateinfo
      on lo_orderdate = d_datekey
      where lo_orderkey <= 900
      group by lo_orderkey
      order by sum(lo_ordtotalprice), lo_orderkey desc
      limit 5
      ) alias1
      )
      group by lo_orderkey
      order by 1, 2 asc
      limit 4
      ) alias2
      order by 2, 1 desc;

      ---------------------+

      lo_orderkey count

      ---------------------+

      4 1
      2 1
      3 6
      1 6

      ---------------------+

      In 1.2 we get the correct answer:
      ---------------------+

      lo_orderkey count

      ---------------------+

      421 1
      389 1
      228 1
      162 1

      ---------------------+

      I ran the interior queries separately and got correct answers. It doesn't seem to break until the final wrapper.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dleeyh Daniel Lee
              Reporter:
              David.Hall David Hall
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

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