[
https://issues.apache.org/jira/browse/HIVE-14123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400531#comment-15400531
]
Lefty Leverenz commented on HIVE-14123:
---------------------------------------
[~pvary], yes a TODOC## label is added to each JIRA issue that needs
documentation, then we remove it when the documentation is done. These labels
make it possible to find out how many issues remain undocumented for a given
release.
I like to add a doc note in the JIRA comments naming any configuration
parameters (so they'll be easy to find in a search) and if I know where the doc
belongs, I give the link.
Ideally the documentation should be done by the developer who created the
patch, in this case you. The Hive wiki covers all releases, so new information
needs to specify the starting release number. We often document things well
before the release just because that's when they're fresh in our minds, even
though this might lead to a bit of confusion among readers.
If you would like to document this now, you will need a Confluence account and
wiki edit permissions as described here: [About This Wiki -- How to get
permission to edit|
https://cwiki.apache.org/confluence/display/Hive/AboutThisWiki#AboutThisWiki-Howtogetpermissiontoedit].
A release note can also give the documentation information. Use the Edit
button (top lefty) to add a release note.
Thanks for asking.
> 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
> Labels: TODOC2.2
> Fix For: 2.2.0
>
> Attachments: HIVE-14123.10.patch, 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.9.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)
