[
https://issues.apache.org/jira/browse/HIVE-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266798#comment-13266798
]
Carl Steinbach commented on HIVE-2996:
--------------------------------------
@Namit: My main concern is that many of the hooks which were committed in
HIVE-2986 reference non-public APIs. For example, I see references to
SessionState, QueryPlan, DDLTask, ExplainTask, HiveOperation, etc. It looks
like one consequence of adding these hooks is that developers will now have to
treat them as de facto public APIs. Does that sound accurate? If so, what's the
proposed policy for handling future changes to these internal APIs? What will
be the process for modifying the hooks which were added in HIVE-2986, and where
will the tests that reference these hooks live? If a change breaks one of these
tests, who is responsible for fixing it?
> minor bug in hooks (NPE)
> ------------------------
>
> Key: HIVE-2996
> URL: https://issues.apache.org/jira/browse/HIVE-2996
> Project: Hive
> Issue Type: Bug
> Reporter: Namit Jain
> Attachments: HIVE-2996.D2991.1.patch
>
>
> NPE in AbstractSmcConfigHook.java
--
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
