[
https://issues.apache.org/jira/browse/HBASE-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667009#comment-13667009
]
Hudson commented on HBASE-8366:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #542 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/542/])
HBASE-8366 HBaseServer logs the full query (Revision 1486232)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/IPCUtil.java
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClient.java
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/QosFunction.java
> 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
