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

Posted to commits@sentry.apache.org by "Sravya Tirukkovalur (JIRA)" <ji...@apache.org> on 2015/08/20 06:11:47 UTC

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

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

Sravya Tirukkovalur updated SENTRY-330:
---------------------------------------
    Issue Type: Improvement  (was: Bug)

> 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.6.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)