[jira] [Created] (TRAFODION-2916) ODB crashes when there are several string truncation warnings during load

["苏锦佩 (JIRA)" <ji...@apache.org>]

苏锦佩 created TRAFODION-2916:
------------------------------

             Summary: ODB crashes when there are several string truncation warnings during load
                 Key: TRAFODION-2916
                 URL: https://issues.apache.org/jira/browse/TRAFODION-2916
             Project: Apache Trafodion
          Issue Type: Bug
          Components: db-utility-odb
            Reporter: 苏锦佩


ODB crashes on windows when there are several string truncation warnings during load. The crash happens when the load has completed and some thread is exiting. In the test case one column was of size varchar(1500) and sometimes data exceeded this size as the actual maximum is 2K. The crash seems to occur regardless of whether warnings are displayed or silently ignored. The crash was not seen after column size was increased to 2K. Several hundred warning rows may be required to see the problem (in a single invocation of ODB). Multiple loading threads may also be needed to see the problem.

step to reproduce:

This is the DDL used, though problem should be visible with other DDL too.

CREATE TABLE TRAFODION.WEBROOT.LOGTABLE_SAMPLE
  (
    TIME_STAMP LARGEINT NO DEFAULT NOT NULL NOT DROPPABLE
  , CLIENTIPADDRESS VARCHAR(100) CHARACTER SET ISO88591
      COLLATE DEFAULT DEFAULT NULL
  , USERNAME VARCHAR(100) CHARACTER SET ISO88591
      COLLATE DEFAULT DEFAULT NULL
  , GROUPID LARGEINT DEFAULT NULL
  , COMPANYID LARGEINT NO DEFAULT NOT NULL NOT DROPPABLE
  , PROXYID LARGEINT DEFAULT NULL
  , FULLORSITELOGGING CHAR(2) CHARACTER SET ISO88591 COLLATE
      DEFAULT DEFAULT NULL
  , POLICYFLAGS CHAR(15) CHARACTER SET ISO88591 COLLATE
      DEFAULT DEFAULT NULL
  , ACTIONSTAKEN CHAR(15) CHARACTER SET ISO88591 COLLATE
      DEFAULT DEFAULT NULL
  , RESPONSESTATUS LARGEINT DEFAULT NULL
  , CONTENTID LARGEINT DEFAULT NULL
  , CONTENTTYPE VARCHAR(100) CHARACTER SET ISO88591
      COLLATE DEFAULT DEFAULT NULL
  , BYTESSERVED LARGEINT DEFAULT NULL
  , REQUESTELAPSEDMS LARGEINT DEFAULT NULL
  , CATEGORYID CHAR(20) CHARACTER SET ISO88591 COLLATE
      DEFAULT DEFAULT NULL
  , MALWARETYPE VARCHAR(50) CHARACTER SET ISO88591 COLLATE
      DEFAULT DEFAULT NULL
  , MALWARENAME VARCHAR(100) CHARACTER SET ISO88591
      COLLATE DEFAULT DEFAULT NULL
  , METHOD CHAR(10) CHARACTER SET ISO88591 COLLATE
      DEFAULT DEFAULT NULL
  , URL VARCHAR(1500) CHARACTER SET ISO88591
      COLLATE DEFAULT DEFAULT NULL
  )
  STORE BY (COMPANYID ASC, TIME_STAMP ASC)
  SALT USING 16 PARTITIONS
       ON (COMPANYID)
  DIVISION BY (cast((TIME_STAMP / 86400000000) AS INTEGER SIGNED NOT NULL))
 ATTRIBUTES ALIGNED FORMAT
  HBASE_OPTIONS
  (
    DATA_BLOCK_ENCODING = 'FAST_DIFF',
    COMPRESSION = 'GZ',
    MEMSTORE_FLUSH_SIZE = '1073741824',
    MAX_FILESIZE = '10737418240'
  )
;

We do not have data. It will be good to generate data maybe using ODB itself with a table that has 2K as the column size for the URL column and then turn around and use it on this DDL with a smaller size for URL column.

Aditional info:
|Specifying fieldtrunc=1 or not using this option at all seems to have some impact on the frequency of occurence of crash.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)