sentry-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <j...@apache.org>
Subject [jira] [Created] (SENTRY-2262) Sentry client is not compatible when connecting to Sentry 2.0
Date Mon, 11 Jun 2018 15:17:00 GMT
Sergio Peña created SENTRY-2262:
-----------------------------------

             Summary: Sentry client is not compatible when connecting to Sentry 2.0
                 Key: SENTRY-2262
                 URL: https://issues.apache.org/jira/browse/SENTRY-2262
             Project: Sentry
          Issue Type: Bug
          Components: Sentry
    Affects Versions: 2.1.0
            Reporter: Sergio Peña


SENTRY-2162 added a new parameter 'entityName' in list_sentry_privileges_by_role() to replace
the 'roleName' parameter. The change was propagated to the SentryPolicyServiceClientDefaultImpl
to use the setEntityName(), but this is causing an incompatibility when connecting to a previous
version of Sentry 2.0.

The reason is that Sentry 2.0 does not accept an empty role name and it does not understand
what entity name. To keep this compatibility, we need to still use the role name as a parameter
in the client code for the rest of 2.x version until the roleName is removed in a major version
of Sentry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message