The queue specific configurations are not hive client specific, they have to be
configured on JobTracker before JT is started up. All the Hive Cli should try
setting is which queue they will want the DAG from hive query to be submitted
to.
So your capacity-scheduler.xml in $HADOOP_CONF_DIR sho
Does anyone know how to export data out with column names? Any help here is
appreciated.
Thanks,
Ranjith
Hello,
I have one instance of HIVE JDBC server running on port 1. Can I run
another
instance on different port ? Would it cause a concurrency issue on the
underlying data warehouse files ? Please clarify.
Thanks,
V.Senthil Kumar
Hi Sreekanth,
When you mention about setting the max task limit, do you mean by executing
set mapred.capacity-scheduler.queue..maximum-capacity = ?
Is it only available on hadoop 0.21?
Thanks,
Rosanna
On 5/1/11 8:42 PM, "Sreekanth Ramakrishnan" wrote:
>
> The design goal of CapacitySchedul
Very cool. What is the non strict option for?
Thanks,
Ranjith
From: Ashish Thusoo
To:
Sent: Mon May 02 16:00:39 2011
Subject: Re: Cross join in Hive.
you could probably just say (1 = 1) in the on clause for the join.
set hive.mapred.mode=nonstrict;
select ...
you could probably just say (1 = 1) in the on clause for the join.
set hive.mapred.mode=nonstrict;
select ... from T1 join T2 on (1 = 1);
Ashish
On May 1, 2011, at 10:27 PM, Raghunath, Ranjith wrote:
Forgot to mentionthe condition for the inner join should be the column set
to 1 in the fir
On Mon, May 2, 2011 at 4:29 PM, Zeus Courtois wrote:
> Hi,
> I am able to issue Hive queries through the Hive JDBC but I cannot find a
> way to set config parameters nor change the job name.
> Is there a way to pass/modify the HiveConf when issuing a JDBC statement?
> I have tried creating my own
Hi,
I am able to issue Hive queries through the Hive JDBC but I cannot find a way
to set config parameters nor change the job name.
Is there a way to pass/modify the HiveConf when issuing a JDBC statement?
I have tried creating my own Session but had not much success by using:
org.apache.hadoop
We've noticed that our Hive jobs appear to be getting slower and slower
every day even though the data set isn't really growing by much.
Here are some run times taken from last month which shows the date and
the duration of the job in minutes:
2010/12/31 -> 19.21667
2011/01/31 -> 24.55
