Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.2
-
None
Description
In test working_tpch1_compareLogOnly/tableMode/autoswitch.sql, we find the following:
SELECT SUM(L_EXTENDEDPRICE * (1 - L_DISCOUNT)) AS REVENUE FROM LINEITEM, PART WHERE ( P_PARTKEY = L_PARTKEY AND P_BRAND = 'Brand#41' AND P_CONTAINER IN ( 'SM CASE', 'SM BOX', 'SM PACK', 'SM PKG') AND L_QUANTITY >= 3 AND L_QUANTITY <= 3 + 1 AND P_SIZE BETWEEN 1 AND 5 AND L_SHIPMODE IN ('AIR', 'AIR REG') AND L_SHIPINSTRUCT = 'DELIVER IN PERSON' ) OR ( P_PARTKEY = L_PARTKEY AND P_BRAND = 'Brand#33' AND P_CONTAINER IN ( 'MED BAG', 'MED BOX', 'MED PKG', 'MED PACK') AND L_QUANTITY >= 14 AND L_QUANTITY <= 14 + 1 AND P_SIZE BETWEEN 1 AND 10 AND L_SHIPMODE IN ('AIR', 'AIR REG') AND L_SHIPINSTRUCT = 'DELIVER IN PERSON' ) OR ( P_PARTKEY = L_PARTKEY AND P_BRAND = 'Brand#45' AND P_CONTAINER IN ( 'LG CASE', 'LG BOX', 'LG PACK', 'LG PKG') AND L_QUANTITY >= 25 AND L_QUANTITY <= 25 + 1 AND P_SIZE BETWEEN 1 AND 15 AND L_SHIPMODE IN ('AIR', 'AIR REG') AND L_SHIPINSTRUCT = 'DELIVER IN PERSON' );
In 1.1 this would cause an autoswitch to mode 0 and the query completes:
-------------
| REVENUE |
-------------
| 607989.6988 |
-------------
1 row in set, 1 warning (15.93 sec)
In 1.2, it doesn't matter what the vtable mode is, we always get this error:
ERROR 1815 (HY000): Internal error: IDB-1000: 'lineitem' and 'part' are not joined.
Attachments
Issue Links
- includes
-
-
- Closed
-
- relates to
-
-
- Closed
-
Activity
The create_calpont_group_by_handler() checks both infinidb_vtable_mode and vtable_status before returns the GROUP BY handler, so query processing in autoswitch mode follows the pre-1.2 behavior.
This bug report is only for the ability to autoswitch, which the patch fixes. However the query still doesn't work in mode 0. See MCOL-1457.
Build verified: 1.2.3-1
server commit:
61f32f2
engine commit:
46cc344
There's more to it than that. It breaks with mode 0. OK, maybe disabling GROUP BY push down would help. Or maybe fixing GROUP BY push down to handle this.
But even so, when in mode 2 (auto fail-over to mode 0), it doesn't auto fail-over. It just fails and never sets REDO_PHASE1. Verified in gdb.