You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2017/11/14 17:13:00 UTC

[jira] [Resolved] (SENTRY-2039) KeyValue is case sensitive and it causes incompatibility issues with external components

     [ https://issues.apache.org/jira/browse/SENTRY-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergio Peña resolved SENTRY-2039.
---------------------------------
    Resolution: Won't Fix

The case-sensitive issue is solved by each of the external components by using a specific model and using the CommonPrivilege interface. My old tests were based on a different Privilege interface (such as IndexerWildcardPrivilege), so my tests were failing, but I learned that Kafka, Solr, hive and Sqoop use the same CommonPrivilege and they work.

By switching the hbase-indexer to the CommonPolicyEngine which uses the CommonPrivilege, then the tests work correctly.

FYI [~akolb]

> KeyValue is case sensitive and it causes incompatibility issues with external components
> ----------------------------------------------------------------------------------------
>
>                 Key: SENTRY-2039
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2039
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 1.8.0
>            Reporter: Sergio Peña
>            Assignee: Sergio Peña
>             Fix For: 2.0.0
>
>         Attachments: SENTRY-2039.1.patch, SENTRY-2039.2.patch, SENTRY-2039.3.patch, SENTRY-2039.4.patch
>
>
> A refactor done on SENTRY-999 changed the way KeyValue.equals() checks for equality. It used to be case insensitive and now it is case sensitive. This may cause issues (like hbase indexer) when policies are written with case insensitive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)