hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-3768) Document JDBC client configuration for secure clusters
Date Thu, 17 Jan 2013 14:30:24 GMT

     [ https://issues.apache.org/jira/browse/HIVE-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lefty Leverenz updated HIVE-3768:
---------------------------------

    Fix Version/s: 0.10.0
           Labels: documentation  (was: )
     Release Note: Document JDBC client config for secure clusters in "Hive Client" user doc
and tidy up the menu.
           Status: Patch Available  (was: Open)

Patch 2 documents the need for hive-site.xml to be in the CLASSPATH of the JDBC client when
configuring Hive on a secure cluster.

This information is added to a "Hive Client" doc, which was converted from the wiki.

The patch adds one doc file and modifies two auxiliary files:

* docs/xdocs/hiveclient.xml is the source doc for Hive client setup

* project.xml adds a menu item for the client setup doc, fixes a misnamed menu item (DDL,
not DML), adds a link to the javadocs, and changes the capitalization of a few menu items

* site.vsl removes menu indentation and changes the copyright year to 2013 in HTML footers
                
> Document JDBC client configuration for secure clusters
> ------------------------------------------------------
>
>                 Key: HIVE-3768
>                 URL: https://issues.apache.org/jira/browse/HIVE-3768
>             Project: Hive
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.9.0
>            Reporter: Lefty Leverenz
>            Assignee: Lefty Leverenz
>              Labels: documentation
>             Fix For: 0.10.0
>
>         Attachments: HIVE-3768.1.patch, HIVE-3768.2.patch
>
>
> Document the JDBC client configuration required for starting Hive on a secure cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message