[
https://issues.apache.org/jira/browse/SENTRY-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120661#comment-14120661
]
SentryQA 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 2 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.hive.TestConfigTool
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-SENTRY-Build/290/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: Bug
> Affects Versions: 1.5.0
> Reporter: Prasad Mujumdar
> Assignee: Ruiming Zhou
> Labels: newbie
> Fix For: 1.5.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)
