[
https://issues.apache.org/jira/browse/SENTRY-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236166#comment-16236166
]
Alexander Kolbasov commented on SENTRY-2028:
--------------------------------------------
Thanks for clarifications. A few questions:
- SENTRY-1159 was committed a while ago - why is this issue only showing up now?
- [~kkalyan] mentions that this issue shows up with Oracle only - what part of
the problem is specific to Oracle? Are we missing some innconsistency between
package.jdo and Oracle schema creation scripts?
- With the SENTRY-1159 fix does it mean that schemas are always created whether
they do exist or not? Or they are only created if they are not defined?
> 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
>
>
> 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)
