You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hrishikesh Gadre (JIRA)" <ji...@apache.org> on 2017/10/30 21:51:00 UTC
[jira] [Updated] (SENTRY-2025) Sentry service permissions metadata
should be tagged with version
[ https://issues.apache.org/jira/browse/SENTRY-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hrishikesh Gadre updated SENTRY-2025:
-------------------------------------
Description: The Sentry service client (SentryGenericServiceClient) interface does not provide the sentry version with which a given permission was created. This information is very useful for writing automated permissions migration tooling (SENTRY-1480), because then the migration tool can look for permissions created for one or more specific Sentry versions for migration purpose. Without this info, the tool will need inputs from the users (which may result in issues with the migration due to wrong inputs). (was: The Sentry service client (SentryGenericServiceClient) interface does not provide the sentry version with which a given permission was created. This information is very useful for writing automated permissions migration tooling (SOLR-1480), because then the migration tool can look for permissions created for one or more specific Sentry versions for migration purpose. Without this info, the tool will need inputs from the users (which may result in issues with the migration due to wrong inputs).)
> Sentry service permissions metadata should be tagged with version
> -----------------------------------------------------------------
>
> Key: SENTRY-2025
> URL: https://issues.apache.org/jira/browse/SENTRY-2025
> Project: Sentry
> Issue Type: Bug
> Components: Service
> Affects Versions: 1.8.0
> Reporter: Hrishikesh Gadre
>
> The Sentry service client (SentryGenericServiceClient) interface does not provide the sentry version with which a given permission was created. This information is very useful for writing automated permissions migration tooling (SENTRY-1480), because then the migration tool can look for permissions created for one or more specific Sentry versions for migration purpose. Without this info, the tool will need inputs from the users (which may result in issues with the migration due to wrong inputs).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)