The simplest solution I can think of is to write some intermediate layer of
code in PIG that uses XMLLoader to convert it to a csv/tsv and then read it in
hive.
From: Sadananda Hegde
To: user@hive.apache.org
Sent: Sunday, September 2, 2012 2:06 PM
Subject: R
e
>>
>> for partitionValue in values
>>
>> hive $HIVEPARAMS -hiveconf partition=$partition -e hivequery.hql
>>
>> and then in hivequery.sql you can refer the variable with
>>
>> where column_name = '${hiveconf:partition}'
>>
&
m_unixtime(unix_timestamp())),3),
hive looks through all the partitions even though the above function can very
well be computed ahead of time and optimize the query. Is this behaviour
intentional ? And is there a workaround other than hardcoding the date or using
a param?
Thanks,
Ramkumar
Thanks mohit.
From: Mohit Gupta
To: user@hive.apache.org; Ramkumar
Sent: Friday, March 16, 2012 4:22 AM
Subject: Re: Same tablename in DESTINATION and FROM clause
No. First write the result in a temp table, then load it into the original
table.
On Thu
Hi,
Does the MR jobs of a hive query write directly to the destination or are the
results of the MR jobs moved to the destination at the end?
To be more precise, is it safe to write query in the following way,
insert overwrite table X
select do_something from X join Y on (some key)
Was little
contents of the UDF is the same as the one given in the above link (i.e. a
simple lowercase function).
Can anyone please suggest a solution? (I also tried re-starting the hive
server just in case, but it was not useful)
Thanks,
Ramkumar