[
https://issues.apache.org/jira/browse/HIVE-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350780#comment-16350780
]
Szehon Ho commented on HIVE-18347:
----------------------------------
Hi Vihang, thanks for the review! Sorry about the late response. But about
the comments, I was under the impression (at least from Thejas's comment about
HIVE-18449) that we wanted to keep the selection policy as a separate knob of
Hive under Hive control, and not via this hook, which was what the review
comment is suggesting? I think HIVE-19449 seems to already give another knob
for offering some predefined selection mechanism, so I think we shouldn't
incorporate all that into a defaultHook that can be over-riden. What do you
think?
> Allow dynamic lookup of Hive Metastores via Consul
> --------------------------------------------------
>
> Key: HIVE-18347
> URL: https://issues.apache.org/jira/browse/HIVE-18347
> Project: Hive
> Issue Type: New Feature
> Components: Metastore
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Priority: Major
> Attachments: HIVE-18347.1.patch, HIVE-18347.2.patch,
> HIVE-18347.3.patch, HIVE-18347.4.patch
>
>
> In our organization, we have deployed HiveMetastore and HiveServer2 on Mesos
> as dynamic services for scalability and flexibility.
> In this architecture, we would like to allow HiveServer2 to dynamically load
> balance between Metastores (which may be scaled up and down or to different
> nodes) for different requests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
