Good point, if SearchProviderBackend/SqoopProviderBackend is detected in the configuration file, we can do the automatically update. Thanks, Gregory.
Best regards, Colin Ma(Ma Jun Jie) -----Original Message----- From: Gregory Chanan [mailto:[email protected]] Sent: Thursday, August 6, 2015 9:55 AM To: [email protected] Subject: Re: [DISCUSS] About clean up unnecessary ProviderBackend Why does the user have to update the configuration file? I assume the SentryGenericProviderBackend has the same capabilities as the SearchProviderBackend/SqoopProviderBackend -- can't we just put in some code that detects the old configuration and automatically updates it to the new one? Maybe only if the old one isn't found? Greg On Wed, Aug 5, 2015 at 6:14 PM, Ma, Junjie <[email protected]> wrote: > Hi, > For the Sentry integration with Solr, Sqoop, I think the > current backend provider for them is not necessary. > SearchProviderBackend and SqoopProviderBackend should be replaced by > SentryGenericProviderBackend. > The SENTRY-828<https://issues.apache.org/jira/browse/SENTRY-828> is to > trace this. > But if we remove these ProviderBackend, user need to change > the configuration file and it may be incompatible with the previous > version, do you think this change is acceptable? > > Best regards, > > Colin Ma(Ma Jun Jie) > >
