[
https://issues.apache.org/jira/browse/HIVE-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161311#comment-14161311
]
Navis commented on HIVE-8319:
-----------------------------
[~thejas] I'm thinking of jetty service for custom management APIs.
Azkaban(workflow) also could be a good candidate for this.
bq. This patch is making the Service interface public. We should mark it with
@public annotation in that case, and probably @unstable or (at least @evolving)
as well.
Done.
bq. The interface also needs some cleanup, so that unused functions are removed
(such as register/unregister)
Done. Now it has init/start/stop/getName/getState.
bq. We should also clarify the public/private api status of the classes within
org.apache.hive.service package
How can I do this? Could you point an example in hive codebase?
> Add configuration for custom services in hiveserver2
> ----------------------------------------------------
>
> Key: HIVE-8319
> URL: https://issues.apache.org/jira/browse/HIVE-8319
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: HIVE-8319.1.patch.txt
>
>
> NO PRECOMMIT TESTS
> Register services to hiveserver2, for example,
> {noformat}
> <property>
> <name>hive.server2.service.classes<name>
>
> <value>com.nexr.hive.service.HiveStatus,com.nexr.hive.service.AzkabanService<value>
> </property>
> <property>
> <name>azkaban.ssl.port<name>
> <name>...<name>
> </property>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
