You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/04/29 20:47:13 UTC

[jira] [Comment Edited] (HIVE-13643) Various enhancements / fixes to llap cli tools

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

Sergey Shelukhin edited comment on HIVE-13643 at 4/29/16 6:47 PM:
------------------------------------------------------------------

What I mean is, if I try to start a cluster w/o a name on command line, with hardcoded registry, the cluster name may become something like
"mynode1.foo.bar,mynode2.foo.bar,mynode3.foo.bar" etc. 
1) Will this even work in Slider and other places?
2) Is this what we want?


was (Author: sershe):
What I mean is, if I try to start a cluster w/o a name on command line, with hardcoded registry, the cluster name may become something like
"mynode1.foo.bar,mynode2.foo.bar,mynode3.foo.bar" etc. 
1) Will this even work?
2) Is this what we want?

> Various enhancements / fixes to llap cli tools
> ----------------------------------------------
>
>                 Key: HIVE-13643
>                 URL: https://issues.apache.org/jira/browse/HIVE-13643
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-13643.01.patch, HIVE-13643.02.patch
>
>
> - BUG - llapstatus does not always produce output (PrintWriter.close)
> - llapstatus should parse hiveconf
> - package llap-cli-log4j2.template
> - Log at the start and end of the script to include parameters
> - Generate logs to a file different from hive.log
> - hive --service llap --name does not propagate the name to the daemons



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