[
https://issues.apache.org/jira/browse/HIVE-16335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949524#comment-15949524
]
Vihang Karajgaonkar edited comment on HIVE-16335 at 3/30/17 6:13 PM:
---------------------------------------------------------------------
Thanks for reporting this [~harschware]. I think you are right. I will take a
look at this and fix it. I think the objective of the feature was to make
beeline connection seemless for the most common use-cases. This is not a
documentation issue but looks like a bug in the code. I think we should change
the code to look for /etc/hive/conf instead of /etc/conf/hive
was (Author: vihangk1):
Thanks for reporting this [~harschware]. I think you are right. I will take a
look at this and fix it.
> documentation error in
> -----------------------
>
> Key: HIVE-16335
> URL: https://issues.apache.org/jira/browse/HIVE-16335
> Project: Hive
> Issue Type: Bug
> Components: Beeline
> Affects Versions: 2.1.1
> Reporter: Tim Harsch
> Assignee: Vihang Karajgaonkar
>
> https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients
> says:
> BeeLine looks for it in ${HIVE_CONF_DIR} location and /etc/conf/hive in that
> order.
> shouldn't it be?
> BeeLine looks for it in ${HIVE_CONF_DIR} location and /etc/hive/conf in that
> order?
> Most distributions I've used have a /etc/hive/conf dir.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
