You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Benjamin Guidarelli (JIRA)" <ji...@apache.org> on 2017/09/05 15:32:00 UTC

[jira] [Created] (KUDU-2133) Master Server Crash from mismatched schemas using Spark Context

Benjamin Guidarelli created KUDU-2133:
-----------------------------------------

             Summary: Master Server Crash from mismatched schemas using Spark Context
                 Key: KUDU-2133
                 URL: https://issues.apache.org/jira/browse/KUDU-2133
             Project: Kudu
          Issue Type: Bug
          Components: java, rpc
    Affects Versions: 1.4.0
            Reporter: Benjamin Guidarelli
         Attachments: 3b055209-58c0-24a8-3cd396a4-4fa7d010.dmp, 6b08ef81-ddb8-8caa-241e8ae7-7800226c.dmp

While creating a table in Kudu using kud-spark KuduContext I omitted the `.nullable(true)` option from several fields when I generated a schema so I could add partitions using schema.newPartialRow.  KuduContext.createTable takes a spark StructType as an argument and adds the nullable(true).  When calling createTable the MasterServer reliably crashes, I think, because of this conflict in nullable fields. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)