gt;
> Eugene
>
>
>
> *From: *Igor Kuzmenko <f1she...@gmail.com>
> *Reply-To: *"user@hive.apache.org" <user@hive.apache.org>
> *Date: *Friday, October 13, 2017 at 2:16 AM
> *To: *"user@hive.apache.org" <user@hive.apache.org>
> *Subje
; <user@hive.apache.org>
Subject: Re: Hive locking mechanism on read partition.
Hi, Eugene.
Tables are not transactional and locks are backed by DbTxnManager.
On Fri, Oct 13, 2017 at 2:30 AM, Eugene Koifman
<ekoif...@hortonworks.com<mailto:ekoif...@hortonworks.com>> wrote:
>
>
>
> Eugene
>
>
>
>
>
> *From: *Igor Kuzmenko <f1she...@gmail.com>
> *Reply-To: *"user@hive.apache.org" <user@hive.apache.org>
> *Date: *Thursday, October 12, 2017 at 3:58 AM
> *To: *"user@hive.apache.org" <user@hive.apache.org>
user@hive.apache.org" <user@hive.apache.org>
Subject: Hive locking mechanism on read partition.
Hello, I'm using HDP 2.5.0.0 with included hive 1.2.1. And I have problem with
locking mechanism.
Most of my queries to hive looks like this.
(1)insert into table results_table partition(tas
According to the documentation link you gave:
"A 'S' lock on table and relevant partition is acquired when a read is
being performed. For all other operations, an 'X' lock is taken on the
partition. However, if the change is only applicable to the newer
partitions, a 'S' lock is acquired on the
Hello, I'm using HDP 2.5.0.0 with included hive 1.2.1. And I have problem
with locking mechanism.
Most of my queries to hive looks like this.
*(1)insert into table results_table partition(task_id=${task_id})*
*select * from data_table where ;*
results_table partitioned by
