You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Zsombor Gegesy (JIRA)" <ji...@apache.org> on 2018/03/23 09:46:00 UTC
[jira] [Updated] (RANGER-2035) Errors accessing servicedefs with
empty implClass with Oracle backend
[ https://issues.apache.org/jira/browse/RANGER-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zsombor Gegesy updated RANGER-2035:
-----------------------------------
Attachment: 0001-RANGER-2035-fix-handling-of-null-implClass-in-servic.patch
> Errors accessing servicedefs with empty implClass with Oracle backend
> ---------------------------------------------------------------------
>
> Key: RANGER-2035
> URL: https://issues.apache.org/jira/browse/RANGER-2035
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 1.0.0, 0.7.1
> Environment: Oracle DB
> Reporter: Zsombor Gegesy
> Assignee: Zsombor Gegesy
> Priority: Major
> Labels: admin, oracle
> Fix For: 0.7.2, 1.1.0, 1.0.1
>
> Attachments: 0001-RANGER-2035-fix-handling-of-null-implClass-in-servic.patch
>
>
> Oracle treats empty strings and nulls as equals - if an empty string is inserted, later, it returns as NULL.
> This cause problems when a service def is created, with implementation classname specified as a zero length string. However, when later it is retrieved or updated or delete, Ranger throws various exceptions. In 1.0.0 a couple of exceptions are fixed, because of RANGER-1377, however in 0.7, there is more NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)