You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "kalyan kumar kalvagadda (JIRA)" <ji...@apache.org> on 2017/11/22 14:43:11 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 ]
kalyan kumar kalvagadda updated SENTRY-330:
-------------------------------------------
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release.
> 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
> Labels: newbie
> Fix For: 2.1.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.4.14#64029)