[
https://issues.apache.org/jira/browse/AMBARI-14478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087783#comment-15087783
]
Yusaku Sako commented on AMBARI-14478:
--------------------------------------
Committed to trunk and branch-2.2.
> Hive settings entry has usability problems
> ------------------------------------------
>
> Key: AMBARI-14478
> URL: https://issues.apache.org/jira/browse/AMBARI-14478
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.2.0
> Reporter: Pallav Kulshreshtha
> Assignee: Pallav Kulshreshtha
> Priority: Minor
> Fix For: 2.2.1
>
> Attachments: AMBARI-14478_branch-2.2.patch, Screen Shot 2015-11-03 at
> 10.03.41 AM.png
>
>
> Hive settings offers autocomplete of a partial set of Hive settings.
> There are a few things annoying about the current behavior, mostly coming
> down to how the UI tries to make the field un-editable.
> This means:
> 1. You can't select the text, it's treated as atomic all-or-nothing.
> 2. A single backspace will delete the entire field.
> 3. You can't edit within the field.
> I guess you could say these are really all the same thing. Yet, strangely if
> I type in from the start I can backspace / edit.
> What I tried was to copy/paste some output from Hive CLI then edit it. When I
> paste hive.auto.convert.join=true into the field, I can't go in and delete
> the "=true" part, I have to only copy hive.auto.convert.join. This is
> annoying from a usability point of view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
