he community. I'll
> follow up in that JIRA ticket for discussion, thanks.
>
>
> From: Andrew Lee
> Sent: Wednesday, October 21, 2015 10:25 AM
> To: dev@hive.apache.org
> Subject: Re: Hard Coded 0 to assign RPC Server port number whe
ticket be "Improvement" or "New Feature" ?
From: Xuefu Zhang
Sent: Tuesday, October 20, 2015 6:39 PM
To: dev@hive.apache.org
Subject: Re: Hard Coded 0 to assign RPC Server port number when
hive.execution.engine=spark
Thanks, Andrew! Yo
n the ports makes it easier since
> we can focus
> on a range to monitor and audit.
>
> Hope this explains the reason why we are asking for this feature.
>
>
> ________________
> From: Xuefu Zhang
> Sent: Monday, October 19, 2015 9:37 PM
>
y, October 19, 2015 1:12 PM
> To: dev@hive.apache.org
> Subject: Re: Hard Coded 0 to assign RPC Server port number when
> hive.execution.engine=spark
>
> Hi Andrew,
>
> RpcServer is an instance launched for each user session. In case of Hive
> CLI, which is for a single us
k security. :(
From: Xuefu Zhang
Sent: Monday, October 19, 2015 1:12 PM
To: dev@hive.apache.org
Subject: Re: Hard Coded 0 to assign RPC Server port number when
hive.execution.engine=spark
Hi Andrew,
RpcServer is an instance launched for each user session. In case of Hive
CLI, whic
Hi Andrew,
RpcServer is an instance launched for each user session. In case of Hive
CLI, which is for a single user, what you said makes sense and the port
number can be configurable. In the context of HS2, however, there are
multiple user sessions and the total is unknown in advance. While +1 sch