[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-2817: Fix Version/s: (was: master) 2.1.0 > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: 2.1.0 > > Attachments: RANGER-2817-V5.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: (was: RANGER-2817-V2.patch) > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V5.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: (was: RANGER-2817-V1.patch) > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V5.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: (was: RANGER-2817-V4.patch) > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V5.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: (was: RANGER-2817-V3.patch) > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V5.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: RANGER-2817-V5.patch > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V5.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: RANGER-2817-V4.patch > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V1.patch, RANGER-2817-V2.patch, > RANGER-2817-V3.patch, RANGER-2817-V4.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: RANGER-2817-V3.patch > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V1.patch, RANGER-2817-V2.patch, > RANGER-2817-V3.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: RANGER-2817-V2.patch > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V1.patch, RANGER-2817-V2.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- Attachment: RANGER-2817-V1.patch > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > Attachments: RANGER-2817-V1.patch > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2817) Service configuration update does not cause policies in the service to get downloaded to plugin
[ https://issues.apache.org/jira/browse/RANGER-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2817: --- External issue URL: https://reviews.apache.org/r/72482/ > Service configuration update does not cause policies in the service to get > downloaded to plugin > --- > > Key: RANGER-2817 > URL: https://issues.apache.org/jira/browse/RANGER-2817 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Abhay Kulkarni >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: master > > > Ranger service configuration variables with names with prefix > "ranger.plugin." are downloaded to Ranger plugins along with the policies in > the Ranger service. However, when such configuration parameter is updated > with a new value, that in itself does not cause the policies (and relevant > service configuration parameters) to be downloaded to plugin when the plugin > requests the download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
