You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/09/08 02:57:20 UTC

[jira] [Commented] (KUDU-1179) Creating table with split keys from the wrong schema may crash Master

    [ https://issues.apache.org/jira/browse/KUDU-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472548#comment-15472548 ] 

Todd Lipcon commented on KUDU-1179:
-----------------------------------

[~danburkert] is this still an issue? I think the code has gone through a lot of changes since ~11 months ago when this was filed.

> Creating table with split keys from the wrong schema may crash Master
> ---------------------------------------------------------------------
>
>                 Key: KUDU-1179
>                 URL: https://issues.apache.org/jira/browse/KUDU-1179
>             Project: Kudu
>          Issue Type: Bug
>          Components: master
>    Affects Versions: GA
>            Reporter: Dan Burkert
>            Assignee: Dan Burkert
>
> We found in https://jira.cloudera.com/browse/KUDU-1105 that supplying split rows from the schema projection of a table will crash the Master server.  We should do the following to fix this:
> * ensuring that the split row schema matches the table schema during table create on the client.
> * check for a null arena during op decode on the server.
> Both of these are fully backwards compatible changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)