[
https://issues.apache.org/jira/browse/HIVE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265192#comment-15265192
]
Siddharth Seth commented on HIVE-13643:
---------------------------------------
No. That won't work. We should add some validation around this when trying to
use hive --service llap. Sparate jira though.
llapstatus will also not work for such clusters. There's some checks and log
messages around that.
> 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)
