[
https://issues.apache.org/jira/browse/HCATALOG-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241823#comment-13241823
]
Alan Gates commented on HCATALOG-332:
-------------------------------------
bq. As for HCatBase*Format. Making it public means that users are free to
subclass this and I believe this is something internal (and should probably be
deprecated in the future).
So this is a semantics question. If we say HCatInputFormat is public but
HCatBaseInputFormat is private, I guess that makes sense. Both must be stable
though, because HCatBaseInputFormat defines part of HCIF's interface.
InputJobInfo.getPartitions() returns a list of PartInfos. InputJobInfo is
stable. It seems meaningless to declare InputJobInfo to have a stable
interface while threatening to evolve classes used in that interface. My
assertion is that stability is cumulative. No part of a stable interface can
be less than stable.
> HCatalog needs interface classification
> ---------------------------------------
>
> Key: HCATALOG-332
> URL: https://issues.apache.org/jira/browse/HCATALOG-332
> Project: HCatalog
> Issue Type: New Feature
> Reporter: Ashutosh Chauhan
> Assignee: Alan Gates
> Fix For: 0.5
>
> Attachments: HCAT-332-2.patch, HCAT-332.patch
>
>
> All the public facing interfaces should be marked for intended audience and
> stability. Ref: HADOOP-5073
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
