n both the view
and the table shows the analizer does indeed pick up the right partition on
both cases (view and table).
From: Mich Talebzadeh
To: user@hive.apache.org; 'cobby cohen'
Sent: Monday, March 16, 2015 9:36 PM
Subject: RE: view over partitioned table
#yiv36648
r multiple
view).Empirical tests, by the show, suggest that indeed, partition optimization
does take place. regards, cobby.
From: "Moore, Douglas"
To: "user@hive.apache.org" ; 'cobby cohen'
Sent: Monday, March 16, 2015 4:19 PM
Subject: Re: view over par
hi,can i execute a hive script within another script?
in the following case:
create table T1(id string)partitioned by (date date);
create view V1(id, date)select id, date from T1
if i do the followingselect id from V1 where date = '2015-04-04'will the query
optimize on T1's partitioning?
and what if V1 is a bit more complex, further depending on othe
done early in the query plan phase and have no
effect on underling infra.
regards,cobby.
> On 12 במרץ 2015, at 23:05, Gopal Vijayaraghavan wrote:
>
> Hi,
>
> No and it¹s a shame because we¹re stuck on some compatibility details with
> this.
>
> The primary is
bucketed column seems great but i dont understand why they are being used for
just for optimizing joins and not where clause (filter).i have a huge table
(billions of records) which includes a field with medium cardinality
(~100,000). user usually filter with that field (at least). using partit
hi, i'm using hdp2.2 (VM) with hive 0.14.0.2.2.0.0-2041.
did the following:
create table t1(id string);create table t2(id string);select
t1.INPUT__FILE__NAME from t1 join t2 on t1.id = t2.id
fails on: Execution failed with exit status: 2
notice this happens also on self joins:select t1_1.INPUT__
