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

Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/02 20:38:00 UTC

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

     [ https://issues.apache.org/jira/browse/KUDU-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Henke resolved KUDU-2133.
-------------------------------
    Fix Version/s: NA
       Resolution: Cannot Reproduce

> 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, master
>    Affects Versions: 1.4.0
>            Reporter: Benjamin Guidarelli
>            Priority: Major
>             Fix For: NA
>
>         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
(v8.3.4#803005)