You can try running derby in multi session mode. I did that , now I can use
Hive web interface and hive CLI simultaneously

On Wednesday, May 28, 2014, Amjad ALSHABANI <ashshab...@gmail.com> wrote:

> OOps, I forgot about that :)
>
> Thanks Dima to mention that.
>
> Actually where I m doing the test using Derby  but on the production
> machine we are using Postgres, so I hope that everything will go well when
> moving to production
>
> Thanx
>
>
> On Wed, May 28, 2014 at 10:52 AM, Dima Machlin 
> <dima.mach...@pursway.com<javascript:_e(%7B%7D,'cvml','dima.mach...@pursway.com');>
> > wrote:
>
>>  You are using the default Derby metastore?
>>
>> There shouldn’t be any problem opening multiple connections to MySQL,
>> Oracle or Postgres.
>>
>>
>>
>>
>>
>> *From:* Amjad ALSHABANI 
>> [mailto:ashshab...@gmail.com<javascript:_e(%7B%7D,'cvml','ashshab...@gmail.com');>]
>>
>> *Sent:* Wednesday, May 28, 2014 11:42 AM
>> *To:* 
>> user@hive.apache.org<javascript:_e(%7B%7D,'cvml','user@hive.apache.org');>
>> *Subject:* HiveServer2 with Hive CLI
>>
>>
>>
>> Hello everybody,
>>
>>
>>
>> I m trying to start hiveserver2 to connect to hive via a PHP application,
>> but in the same time I would like to keep connecting Hive CLI ( hive> ) on
>> the same machine to execute some request manually. It seems that it is not
>> possilbe to do so   (the Hive thrift server seems to lock the metastore ).
>>
>>
>>
>> Is there a way to configure Hive and Hiveserver2 so they could both work
>> together on same machine.
>>
>> I ve seen that using beeline cli may solve this issue but I m not aiming
>> to move now to this solution since it is a production machine and moving to
>> new CLI would cost me some time
>>
>>
>>
>>
>>
>> Cheers
>>
>>
>>
>> Amjad
>>
>>
>>
>>
>>
>>
>>
>> ************************************************************************************
>> This footnote confirms that this email message has been scanned by
>> PineApp Mail-SeCure for the presence of malicious code, vandals &
>> computer viruses.
>>
>> ************************************************************************************
>>
>
>

Reply via email to