[
https://issues.apache.org/jira/browse/SENTRY-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210051#comment-15210051
]
Hadoop QA commented on SENTRY-1103:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12795179/SENTRY-1103.002-SENTRY-999.patch
against SENTRY-999.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/1386/console
This message is automatically generated.
> Authorizable names' case sensitivity must be decided by plugins
> ---------------------------------------------------------------
>
> Key: SENTRY-1103
> URL: https://issues.apache.org/jira/browse/SENTRY-1103
> Project: Sentry
> Issue Type: Sub-task
> Reporter: Ashish K Singh
> Assignee: Colin Ma
> Attachments: SENTRY-1103.001-SENTRY-999.patch,
> SENTRY-1103.002-SENTRY-999.patch
>
>
> With more and more components relying on sentry for authorization, it really
> makes sense to have the case-sensitivity configurable. We can keep the
> current behavior as default. However, for use cases like Kafka, it makes
> sense to have authorizable names case sensitive. For instance, a topic
> resource in Kafka can have case sensitive values, like, topic1 and TOPIC1 are
> two completely different valid topic resource instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
