hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <>
Subject [jira] [Commented] (HIVE-6332) HCatConstants Documentation needed
Date Fri, 07 Mar 2014 00:38:43 GMT


Sushanth Sowmyan commented on HIVE-6332:

+ Added wiki link with original version in :

+ Fixed "patttern"

Re:, I guess the question is whether this is user-facing (user of HCatalog,
could be a developer of some other tool that uses HCat) or developer-facing (someone who's
developing hive/hcat) - with this doc, I went for user-facing, and they might not need to
know about HCatConstants, which I see as internal-facing. I have given it a token introduction
though, and am wondering how I can flesh that out a bit better.

Re: vs : Oh shoot. >< Good catch, we should have caught that
when hcatalog.hive.client.cache.expiry.time was added, but we didn't, and hcatalog.hive.client.cache.disabled,
which was added recently followed that pattern. However, that makes that public api we should
respect. I'll start another bug updating that and adding a deprecation cycle for it, but we'd
get around to removing this only in hive-0.16 timeframe.

Re: pig section, I'll try to clean that up a bit. HCatStorerWrapper does it automatically
for the user, if they use it instead of HCatStorer, and if they use HCatStorer as is, but
want to specify a custom location, they need to set that parameter in pig before invoking
the storer. I'll put in some code examples. The Storage directives section in general could
use code examples, I'll add them in.

Re: Data promotion, yes, that's what that means. I'll edit it to reflect that better.

> HCatConstants Documentation needed
> ----------------------------------
>                 Key: HIVE-6332
>                 URL:
>             Project: Hive
>          Issue Type: Task
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
> HCatConstants documentation is near non-existent, being defined only as comments in code
for the various parameters. Given that a lot of api winds up being implemented as knobs that
can be tweaked here, we should have a public facing doc for this.

This message was sent by Atlassian JIRA

View raw message