[
https://issues.apache.org/jira/browse/HIVE-14123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384207#comment-15384207
]
Peter Vary commented on HIVE-14123:
-----------------------------------
Currently we have the following configuration variables (before the patch as
well):
- Compatibility mode - use the hive-site.xml, and hive config variables as ever
- Beeline mode
- beeline.properties configuration file from the following directories:
HOME/.beeline/ on UNIX, and HOME/beeline/ on Windows.
- Command line options - these overwrite the ones stored in
beeline.properties
I have decided not to change this separation in my patch, and my changes only
effect beeline in beeline mode.
It is not trivial to use the HiveConf object (hive configuration) in beeline
mode, since it is designed specifically to read the hive-site.xml and other
server side configurations, and initialized during the server startup. And even
after refactoring this code, since beeline is a client side program, it is
debatable which set of variables should be used (server side/client side).
There is a different jira - HIVE-13688 -, which more or less addresses the same
issue (HiveConf variable substitution).
> Add beeline configuration option to show database in the prompt
> ---------------------------------------------------------------
>
> Key: HIVE-14123
> URL: https://issues.apache.org/jira/browse/HIVE-14123
> Project: Hive
> Issue Type: Improvement
> Components: Beeline, CLI
> Affects Versions: 2.2.0
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Minor
> Attachments: HIVE-14123.2.patch, HIVE-14123.3.patch,
> HIVE-14123.4.patch, HIVE-14123.5.patch, HIVE-14123.6.patch,
> HIVE-14123.7.patch, HIVE-14123.8.patch, HIVE-14123.patch
>
>
> There are several jira issues complaining that, the Beeline does not respect
> hive.cli.print.current.db.
> This is partially true, since in embedded mode, it uses the
> hive.cli.print.current.db to change the prompt, since HIVE-10511.
> In beeline mode, I think this function should use a beeline command line
> option instead, like for the showHeader option emphasizing, that this is a
> client side option.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
