Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 5 Dec 2014 23:47:12 +0000 (UTC)
From: "Sushanth Sowmyan (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12758767.1417472550000.89560.1417823232860@Atlassian.JIRA>
In-Reply-To: <JIRA.12758767.1417472550000@Atlassian.JIRA>
References: <JIRA.12758767.1417472550000@Atlassian.JIRA>
 <JIRA.12758767.1417472550582@arcas>
Subject: [jira] [Updated] (HIVE-9001) Ship with log4j.properties file that
 has a reliable time based rolling policy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-9001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sushanth Sowmyan updated HIVE-9001:
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.15.0
           Status: Resolved  (was: Patch Available)

Committed to trunk. Thanks, Hari!

> Ship with log4j.properties file that has a reliable time based rolling policy
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-9001
>                 URL: https://issues.apache.org/jira/browse/HIVE-9001
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Hari Sankar Sivarama Subramaniyan
>            Assignee: Hari Sankar Sivarama Subramaniyan
>             Fix For: 0.15.0
>
>         Attachments: HIVE-9001.1.patch
>
>
> The hive log gets locked by the hive process and cannot be rolled in windows OS.
> Install Hive in  Windows, start hive, try and rename hive log while Hive is running. 
> Wait for log4j tries to rename it and it will throw the same error as it is locked by the process.
> The changes in https://issues.apache.org/bugzilla/show_bug.cgi?id=29726 should be integrated to Hive for a reliable rollover.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)