Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.4.2
-
None
-
None
-
1um 4 pm
-
2020-4, 2020-5, 2020-6, 2020-7
Description
Customer reported error and Support was able to reproduce on a single server system running 1.4.2. It as customer reported, it did successfully work on 1.2.5.
This issue is within the new 1.4.2 Columnstore/Server instance that does not occur on 1.2.5 Columnstore.
The group by order seems to be handled differently now. Both 1.4.2 and 1.2.5 instances tables are the same, but when the same query is run, it errors on 1.4.2 only.
Data will be in the next comments as confidential
Build verified: 1.4.3-5 hot fix, Azure 20200401.6
MariaDB [sc]> CREATE TABLE `bovine_assay_system` (
-> `platform_id` smallint(6) DEFAULT NULL,
-> `snp_name` varchar(48) DEFAULT NULL,
-> `assay_id` int(11) DEFAULT NULL,
-> `probe_id` int(11) DEFAULT NULL,
-> `ref_genome` varchar(64) DEFAULT NULL,
-> `variant_id` int(11) DEFAULT NULL,
-> `chrom` tinyint(4) DEFAULT NULL,
-> `cchrom` varchar(64) DEFAULT NULL,
-> `position` bigint(20) DEFAULT NULL,
-> `report_strand` tinyint(4) DEFAULT NULL,
-> `strand` tinyint(4) DEFAULT NULL,
-> `flip` tinyint(4) DEFAULT NULL,
-> `allele_group` varchar(7) DEFAULT NULL,
-> `design_allele1` char(1) DEFAULT NULL,
-> `design_allele2` char(1) DEFAULT NULL,
-> `ref` char(1) DEFAULT NULL,
-> `allele_count` tinyint(4) DEFAULT NULL
-> ) ENGINE=Columnstore DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.217 sec)
MariaDB [sc]> with parentage as (select distinct variant_id,ref_genome,chrom from sc.bovine_assay_system where ref_genome = 'ARS-UCDv1.2.fasta' and snp_name like '%Parent%' group by variant_id,ref_genome,chrom
-> ) select distinct variant_id,ref_genome,chrom from sc.bovine_assay_system where ref_genome ='ARS-UCDv1.2.fasta' and platform_id!=45 and variant_id not in (select variant_id from parentage)
-> group by variant_id,ref_genome,chrom having count(distinct platform_id)=19;
Empty set (0.205 sec)