[
https://issues.apache.org/jira/browse/SENTRY-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238132#comment-16238132
]
kalyan kumar kalvagadda edited comment on SENTRY-2028 at 11/3/17 6:27 PM:
--------------------------------------------------------------------------
[~spena]I think it would have an mistake. If you look at the patch submitted
for SENTRY-1159, it is adding this property "datanucleus.schema.autoCreateAll"
in couple of places. In can be set to true is other places but not in
SentryStore. Could be a copy/paste issue. As it will not cause any test
failures for derby, it was off the radar.
was (Author: kkalyan):
I think it would have an mistake. If you look at the patch submitted for
SENTRY-1159, it is adding this property "datanucleus.schema.autoCreateAll" in
couple of places. In can be set to true is other places but not in SentryStore.
Could be a copy/paste issue. As it will not cause any test failures for derby,
it was off the radar.
> Avoid datanucleus to create/update database schema
> --------------------------------------------------
>
> Key: SENTRY-2028
> URL: https://issues.apache.org/jira/browse/SENTRY-2028
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Priority: Major
> Attachments: SENTRY-2028.001.patch, SENTRY-2028.001.patch
>
>
> With the current default datanucleus configuration, datanucleus tries to
> update the database schema. This is not desired as the schema creation and
> update happens from schemaTool using sql files.
> If this jira is resolved, issues reported in SENTRY-1934 and SENTRY-2011
> will not be seen. I feel we should revert code changes done for these jira's
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
