[jira] [Commented] (SENTRY-330) Update Derby schema script to enforce non-null constraint

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on SENTRY-330:
----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12662782/SENTRY-330.patch against master.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1323/console

This message is automatically generated.

> Update Derby schema script to enforce non-null constraint
> ---------------------------------------------------------
>
>                 Key: SENTRY-330
>                 URL: https://issues.apache.org/jira/browse/SENTRY-330
>             Project: Sentry
>          Issue Type: Improvement
>    Affects Versions: 1.5.0
>            Reporter: Prasad Mujumdar
>            Assignee: Ruiming Zhou
>              Labels: newbie
>             Fix For: 1.8.0
>
>         Attachments: SENTRY-330.patch
>
>
> Currently Derby schema script is not consistent with setting bunch of columns as non-null. We need to keep this in sync with other schema scripts. Since derby is used for unit test, this can cause issues to got through unit tests and fail in the real deployments.



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