[MCOL-241] DBT3 query 12 returned an empty result set Created: 2016-07-01  Updated: 2016-09-02  Resolved: 2016-09-02

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr
Affects Version/s: 1.0.1
Fix Version/s: 1.0.2

Type: Bug Priority: Critical
Reporter: Daniel Lee (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
is part of MCOL-280 Beta issues Closed

 Description   

Build tested: alpha 1.0.1

mscadmin> getsoft
getsoftwareinfo Fri Jul 1 18:33:11 2016

Name : mariadb-columnstore-platform
Version : 1.0
Release : 1
Architecture: x86_64
Install Date: Fri 24 Jun 2016 07:28:00 PM UTC

Create a DBT3 (TPCH) database and load 1gb of data

execute the query #12

select
l_shipmode,
sum(case
when o_orderpriority = '1-URGENT'
or o_orderpriority = '2-HIGH'
then 1
else 0
end) as high_line_count,
sum(case
when o_orderpriority <> '1-URGENT'
and o_orderpriority <> '2-HIGH'
then 1
else 0
end) as low_line_count
from
orders,
lineitem
where
o_orderkey = l_orderkey
and l_shipmode in ('REG AIR', 'RAIL')
and l_commitdate < l_receiptdate
and l_shipdate < l_commitdate
and l_receiptdate >= '1994-01-01'
and l_receiptdate < date_add( '1994-01-01' , interval 1 year)
group by
l_shipmode
order by
l_shipmode;

The same query on InnoDB returned:

-----------------------------------------

l_shipmode high_line_count low_line_count

-----------------------------------------

RAIL 6313 9320
REG AIR 6246 9245

-----------------------------------------
2 rows in set (32.63 sec)



 Comments   
Comment by Daniel Lee (Inactive) [ 2016-09-02 ]

The empty resultset issue was caused by the bug described in MCOL-281.

Generated at Thu Feb 08 02:19:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.