Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-4527

Columns in Kudu tables created from Impala default to "NOT NULL"

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: Kudu_Impala
    • Fix Version/s: Impala 2.8.0
    • Component/s: Frontend
    • Labels:
    • Docs Text:
      By default non-key columns are nullable unless specified otherwise.
    • Target Version:

      Description

      Kudu tables created by Impala columns default to "NOT NULL".
      This behavior opposes Oracle, Teradata, MSSqlserver, MySQL...

      Table DDL

      CREATE TABLE store_sales_kudu (
       ss_sold_date_sk int ,
       ss_ticket_number bigint,
       ss_item_sk bigint,
       ss_sold_time_sk int ,
      primary key (ss_sold_date_sk,ss_ticket_number,ss_item_sk))
      distribute by hash (ss_sold_date_sk,ss_ticket_number,ss_item_sk) into 400 buckets
      STORED AS KUDU
      tblproperties ('kudu.master_addresses' = 'foor.com:7051');
      

      DML

       insert into store_sales_kudu values (1,1,1,null);
      

      Error

      WARNINGS: Row with null value violates nullability constraint on table 'impala::tpcds_10_kudu.store_sales_kudu'.
      

        Attachments

          Activity

            People

            • Assignee:
              dtsirogiannis Dimitris Tsirogiannis
              Reporter:
              mmokhtar Mostafa Mokhtar
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: