[ 
https://issues.apache.org/jira/browse/DRILL-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053152#comment-17053152
 ] 

ASF GitHub Bot commented on DRILL-7620:
---------------------------------------

paul-rogers commented on issue #2010: DRILL-7620: Fix plugin mutability issues
URL: https://github.com/apache/drill/pull/2010#issuecomment-595660829
 
 
   Updated to include fixes for 
[DRILL-7620](https://issues.apache.org/jira/browse/DRILL-7624).
   
   Also, out of an abundance of caution, restored two method changes to avoid 
breaking third-party plugins. (Plugins in Drill were previously updated to use 
the new methods.)
   
   Added tests to reproduce the issue in DRILL-7620 using a "known bad" mock 
plugin. Reran all unit tests, which passed.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Storage plugin update page shows that a plugin is disabled though it is 
> actually enabled.
> -----------------------------------------------------------------------------------------
>
>                 Key: DRILL-7620
>                 URL: https://issues.apache.org/jira/browse/DRILL-7620
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.18.0
>            Reporter: Anton Gozhiy
>            Assignee: Paul Rogers
>            Priority: Blocker
>             Fix For: 1.18.0
>
>
> *Steps to reproduce:*
> # On Web UI, open storage page
> # Disable some plugin (e.g. "cp")
> # Enable this plugin (It is displayed in "enabled" section now)
> # Update the plugin, look at the "enabled" property
> *Expected result:*
> "enabled": true
> *Actual result:*
> "enabled": false
> *Note:* Though it is displayed as disabled in the config, queries to it are 
> working.
> *Workaround:* Enable it again.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to