Hi all,

is it possible to set: mapreduce.map.log.level &
mapreduce.reduce.log.level, within some config file?

At the moment I have to remember to set these at the start of a hive
session, or script.

Cheers,

Krishna

if you want this to be set at every query you execute best would have a
hiverc file and then include it as hive -i hiverc

alternatively, you can create a .hiverc into your home directory and set
the parameters you want, these will be included in each session
On Fri, Dec 14, 2012 at 4:05 PM, Krishna Rao <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> is it possible to set: mapreduce.map.log.level &
> mapreduce.reduce.log.level, within some config file?
>
> At the moment I have to remember to set these at the start of a hive
> session, or script.
>
> Cheers,
>
> Krishna
>

--
Nitin Pawar

Hi Krishna,

You can also set these properties in the mapred-site.xml, but this would
require a restart of your cluster.

Ted.

Ted Reynolds
Technical Support Engineer
Hortonworks
Work Phone: 408-645-7079

<http://hortonworks.com/download/>

On Fri, Dec 14, 2012 at 2:44 AM, Nitin Pawar <[EMAIL PROTECTED]>wrote:

> if you want this to be set at every query you execute best would have a
> hiverc file and then include it as hive -i hiverc
>
> alternatively, you can create a .hiverc into your home directory and set
> the parameters you want, these will be included in each session
>
>
> On Fri, Dec 14, 2012 at 4:05 PM, Krishna Rao <[EMAIL PROTECTED]>wrote:
>
>> Hi all,
>>
>> is it possible to set: mapreduce.map.log.level &
>> mapreduce.reduce.log.level, within some config file?
>>
>> At the moment I have to remember to set these at the start of a hive
>> session, or script.
>>
>> Cheers,
>>
>> Krishna
>>
>
>
>
> --
> Nitin Pawar
>

Thanks for the replies.

I went for the hiverc option. Unfortunately, with the verion of hive I'm
using, it meant I had to place the file in a bin directory. Our sys admin
was not pleased, but it look's like that issue is fixed in a later version
of Hive (https://issues.apache.org/jira/browse/HIVE-2911)!

On 14 December 2012 17:10, Ted Reynolds <[EMAIL PROTECTED]> wrote:

> Hi Krishna,
>
> You can also set these properties in the mapred-site.xml, but this would
> require a restart of your cluster.
>
> Ted.
>
> Ted Reynolds
> Technical Support Engineer
> Hortonworks
> Work Phone: 408-645-7079
>
> <http://hortonworks.com/download/>
>
>
>
> On Fri, Dec 14, 2012 at 2:44 AM, Nitin Pawar <[EMAIL PROTECTED]>wrote:
>
>> if you want this to be set at every query you execute best would have a
>> hiverc file and then include it as hive -i hiverc
>>
>> alternatively, you can create a .hiverc into your home directory and set
>> the parameters you want, these will be included in each session
>>
>>
>> On Fri, Dec 14, 2012 at 4:05 PM, Krishna Rao <[EMAIL PROTECTED]>wrote:
>>
>>> Hi all,
>>>
>>> is it possible to set: mapreduce.map.log.level &
>>> mapreduce.reduce.log.level, within some config file?
>>>
>>> At the moment I have to remember to set these at the start of a hive
>>> session, or script.
>>>
>>> Cheers,
>>>
>>> Krishna
>>>
>>
>>
>>
>> --
>> Nitin Pawar
>>
>
>

Krishna,
I usually put it in my home directory and that works. Did you try that?
HIVE-2911, adds another location to where it can be picked up from. If your
present version supports .hiverc (which is most likely the case), home
directory should work as well.

Mark

On Mon, Dec 17, 2012 at 5:44 AM, Krishna Rao <[EMAIL PROTECTED]> wrote:

> Thanks for the replies.
>
> I went for the hiverc option. Unfortunately, with the verion of hive I'm
> using, it meant I had to place the file in a bin directory. Our sys admin
> was not pleased, but it look's like that issue is fixed in a later version
> of Hive (https://issues.apache.org/jira/browse/HIVE-2911)!
>
>
>
> On 14 December 2012 17:10, Ted Reynolds <[EMAIL PROTECTED]> wrote:
>
>> Hi Krishna,
>>
>> You can also set these properties in the mapred-site.xml, but this would
>> require a restart of your cluster.
>>
>> Ted.
>>
>> Ted Reynolds
>> Technical Support Engineer
>> Hortonworks
>> Work Phone: 408-645-7079
>>
>> <http://hortonworks.com/download/>
>>
>>
>>
>> On Fri, Dec 14, 2012 at 2:44 AM, Nitin Pawar <[EMAIL PROTECTED]>wrote:
>>
>>> if you want this to be set at every query you execute best would have a
>>> hiverc file and then include it as hive -i hiverc
>>>
>>> alternatively, you can create a .hiverc into your home directory and set
>>> the parameters you want, these will be included in each session
>>>
>>>
>>> On Fri, Dec 14, 2012 at 4:05 PM, Krishna Rao <[EMAIL PROTECTED]>wrote:
>>>
>>>> Hi all,
>>>>
>>>> is it possible to set: mapreduce.map.log.level &
>>>> mapreduce.reduce.log.level, within some config file?
>>>>
>>>> At the moment I have to remember to set these at the start of a hive
>>>> session, or script.
>>>>
>>>> Cheers,
>>>>
>>>> Krishna
>>>>
>>>
>>>
>>>
>>> --
>>> Nitin Pawar
>>>
>>
>>
>

That's not true, you don't need to restart the cluster.

Changing client-side mapredi-site.xml is the correct solution.

HTH,
+Vinod

On Dec 14, 2012, at 9:10 AM, Ted Reynolds wrote:

> Hi Krishna,
>
> You can also set these properties in the mapred-site.xml, but this would require a restart of your cluster.
>
> Ted.
>
> Ted Reynolds
> Technical Support Engineer
> Hortonworks
> Work Phone: 408-645-7079
>
>
>
>
>
> On Fri, Dec 14, 2012 at 2:44 AM, Nitin Pawar <[EMAIL PROTECTED]> wrote:
> if you want this to be set at every query you execute best would have a hiverc file and then include it as hive -i hiverc
>
> alternatively, you can create a .hiverc into your home directory and set the parameters you want, these will be included in each session
>
>
> On Fri, Dec 14, 2012 at 4:05 PM, Krishna Rao <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> is it possible to set: mapreduce.map.log.level & mapreduce.reduce.log.level, within some config file?
>
> At the moment I have to remember to set these at the start of a hive session, or script.
>
> Cheers,
>
> Krishna
>
>
>
> --
> Nitin Pawar
>

On 18 December 2012 02:05, Mark Grover <[EMAIL PROTECTED]> wrote:

> I usually put it in my home directory and that works. Did you try that?
I need it to work for all users. So the cleanest non-duplicating solution,
seems to be in the hive bin directory (and then conf dir, when I upgrade
hive).