[ 
https://issues.apache.org/jira/browse/HIVE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083674#comment-14083674
 ] 

Lefty Leverenz commented on HIVE-6226:
--------------------------------------

GET version/hive and version/hadoop are documented now and listed in the 
WebHCat Reference umbrella page, with cross references from the POST hive, 
mapreduce/streaming, and mapreduce/jar pages:

* [WebHCat Reference | 
https://cwiki.apache.org/confluence/display/Hive/WebHCat+Reference]
** [GET version/hive | 
https://cwiki.apache.org/confluence/display/Hive/WebHCat+Reference+VersionHive]
** [GET version/hadoop | 
https://cwiki.apache.org/confluence/display/Hive/WebHCat+Reference+VersionHadoop]
*** [POST hive | 
https://cwiki.apache.org/confluence/display/Hive/WebHCat+Reference+Hive]
*** [POST mapreduce/streaming | 
https://cwiki.apache.org/confluence/display/Hive/WebHCat+Reference+MapReduceStream]
*** [POST mapreduce/jar | 
https://cwiki.apache.org/confluence/display/Hive/WebHCat+Reference+MapReduceJar]

Please review and correct or improve as needed.

> It should be possible to get hadoop, hive, and pig version being used by 
> WebHCat
> --------------------------------------------------------------------------------
>
>                 Key: HIVE-6226
>                 URL: https://issues.apache.org/jira/browse/HIVE-6226
>             Project: Hive
>          Issue Type: New Feature
>          Components: WebHCat
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>             Fix For: 0.13.0
>
>         Attachments: HIVE-6226.2.patch, HIVE-6226.patch
>
>
> Calling /version on WebHCat tells the caller the protocol verison, but there 
> is no way to determine the versions of software being run by the applications 
> that WebHCat spawns.  
> I propose to add an end-point: /version/\{module\} where module could be pig, 
> hive, or hadoop.  The response will then be:
> {code}
> {
>   "module" : _module_name_,
>   "version" : _version_string_
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to