Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 24 May 2013 22:07:20 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12643033.1366232607223.20342.1369433240638@arcas>
In-Reply-To: <JIRA.12643033.1366232607223@arcas>
References: <JIRA.12643033.1366232607223@arcas>
Subject: [jira] [Updated] (HBASE-8366) HBaseServer logs the full query.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-8366:
-------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Thanks lads.  Applied the patch (w/ Andrew's fix) to 0.95 and trunk.
                
> HBaseServer logs the full query.
> --------------------------------
>
>                 Key: HBASE-8366
>                 URL: https://issues.apache.org/jira/browse/HBASE-8366
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.95.0
>            Reporter: Nicolas Liochon
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.98.0, 0.95.1
>
>         Attachments: 8366.txt, 8366.v1.patch, 8366v2.txt
>
>
> We log the query when we have an error. As a results, the logs are not readable when using stuff like multi.
> As a side note, this is as well a security issue (no need to encrypt the network and the storage if the logs contain everything). I'm not removing the full log line here; but just ask and I do it :-).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira