create table with nullable primary key of varchar type causes assertion failure

Bug #1367936 reported by Suresh Subbiah on 2014-09-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trafodion
Fix Committed
Medium
Suresh Subbiah

Bug Description

cqd ALLOW_NULLABLE_UNIQUE_KEY_CONSTRAINT 'on' ;

CREATE TABLE TRAFODION.OSSDBA.COUNTRY
  (
    COUNTRY_NAME VARCHAR(40 BYTES) CHARACTER SET UTF8
      NOT NULL NOT DROPPABLE
  , ISO_CODE VARCHAR(3 BYTES) CHARACTER SET UTF8
      COLLATE DEFAULT DEFAULT NULL
  , HP_CODE VARCHAR(4 BYTES) CHARACTER SET UTF8
      COLLATE DEFAULT DEFAULT NULL
  , REGION VARCHAR(30 BYTES) CHARACTER SET UTF8
      COLLATE DEFAULT DEFAULT NULL
  , SUBREGION VARCHAR(30 BYTES) CHARACTER SET UTF8
      COLLATE DEFAULT DEFAULT NULL
  , IN_BACKLOG_SHIP VARCHAR(1 BYTE) CHARACTER SET UTF8 COLLATE
      DEFAULT DEFAULT NULL
  , ISO3_CODE VARCHAR(3 BYTES) CHARACTER SET UTF8
      COLLATE DEFAULT DEFAULT NULL
  , HP_REGION VARCHAR(6 BYTES) CHARACTER SET UTF8
      COLLATE DEFAULT DEFAULT NULL
  )
  STORE BY (COUNTRY_NAME ASC)
  SALT USING 16 PARTITIONS
;

gives
*** ERROR[2006] Internal error: assertion failure (keyColOffset == encodedKeyLen) in file ../optimizer/NATable.cpp at line 1553.

tags: added: sql-cmp
Changed in trafodion:
milestone: r1.0 → r1.1
Suresh Subbiah (suresh-subbiah) wrote :

This problem was addressed some time ago. The problem no longer shows in a recent build.

Changed in trafodion:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers