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

kalyan kumar kalvagadda updated SENTRY-2271:
--------------------------------------------
    Description: 
SentrySchema classes still use "MetaStore" instead of sentrystore for method 
names and even in logs. It should be corrected. Below is one such example.

 

SentryStoreSchemaInfo has log which still refer "Metastore". Here is an example
{noformat}
throw new SentryUserException("Unknown version specified for upgrade "
 + fromSchemaVer + " Metastore schema may be too old or newer");

{noformat}
 

We need to asses if there are any other message like like and fix them.

  was:
SentryStoreSchemaInfo has log which still refer "Metastore". Here is an example

{noformat}

throw new SentryUserException("Unknown version specified for upgrade "
 + fromSchemaVer + " Metastore schema may be too old or newer");

{noformat}

 

We need to asses if there are any other message like like and fix them.


> Wrong log messages/method names in SentrySchema related classes.
> ----------------------------------------------------------------
>
>                 Key: SENTRY-2271
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2271
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 2.1.0
>            Reporter: kalyan kumar kalvagadda
>            Assignee: Arjun Mishra
>            Priority: Major
>         Attachments: SENTRY-2271.01.patch
>
>
> SentrySchema classes still use "MetaStore" instead of sentrystore for method 
> names and even in logs. It should be corrected. Below is one such example.
>  
> SentryStoreSchemaInfo has log which still refer "Metastore". Here is an 
> example
> {noformat}
> throw new SentryUserException("Unknown version specified for upgrade "
>  + fromSchemaVer + " Metastore schema may be too old or newer");
> {noformat}
>  
> We need to asses if there are any other message like like and fix them.



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

Reply via email to