You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/08 12:02:00 UTC

[jira] [Updated] (AMBARI-24421) Invalid description on Hive configuration

     [ https://issues.apache.org/jira/browse/AMBARI-24421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated AMBARI-24421:
------------------------------------
    Labels: pull-request-available  (was: )

> Invalid description on Hive configuration 
> ------------------------------------------
>
>                 Key: AMBARI-24421
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24421
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.6.1, 2.7.0
>            Reporter: Kwanghee Park
>            Priority: Trivial
>              Labels: pull-request-available
>         Attachments: image-2018-08-08-19-57-11-493.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> I've just found a wrong description at  Advanced *+hive-interactive-site+* -> "Allow custom queues" in Hive configuration -> Advanced Tab.
> If you drag and put the field of "Allow custom queues", you may see Its description.
>  
> !image-2018-08-08-19-57-11-493.png!
> The options explain to use "yes", "no", "ignore" in Ambari but corresponding code is  "true", "false", "ignore" in Apache Hive(common/src/java/org/apache/hadoop/hive/conf/HiveConf.java) 
> {code:java}
> HIVE_SERVER2_TEZ_SESSION_CUSTOM_QUEUE_ALLOWED("hive.server2.tez.sessions.custom.queue.allowed",
>   "true", new StringSet("true", "false", "ignore"),
>   "Whether Tez session pool should allow submitting queries to custom queues. The options\n" +
>   "are true, false (error out), ignore (accept the query but ignore the queue setting)."),
> {code}
> Because of such inconsistent description, I had typed "yes" and had save the configuration and then restarted "Hive Interactive Service" however the service stopped with an error and I spent a couple of hours to solve it.
> Thus we have to fix this description.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)