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

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

GitHub user jaltekruse opened a pull request:

    https://github.com/apache/drill/pull/343

    DRILL-2653: Improve web UI experience when there is an error in a sto…

    …rage plugin configuration

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jaltekruse/incubator-drill 
2653-web-ui-storage-plugin-conf-error

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/343.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #343
    
----
commit 3d12ac5d97f32657643196ade616643fa62735e5
Author: Jason Altekruse <[email protected]>
Date:   2016-01-28T18:01:30Z

    DRILL-2653: Improve web UI experience when there is an error in a storage 
plugin configuration

----


> All additions to storage plugin configuration gets wiped out if info is not 
> correct 
> ------------------------------------------------------------------------------------
>
>                 Key: DRILL-2653
>                 URL: https://issues.apache.org/jira/browse/DRILL-2653
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - HTTP
>    Affects Versions: 0.9.0
>            Reporter: Krystal
>             Fix For: Future
>
>         Attachments: DRILL-2653.1.patch.txt
>
>
> Whenever a user enters an invalid information into a storage plugin 
> configuration, the entire data gets wiped out.  This can be frustrating to 
> users if alot of information has been entered.  The data should be retained 
> on the screen to allow users correct the mistakes rather than having to write 
> all the information over again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to