[jira] [Commented] (ACCUMULO-2938) Investigate logging on KeyExtent to ensure no data leakage

2014-06-23 Thread Sean Busbey (JIRA)
[ https://issues.apache.org/jira/browse/ACCUMULO-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041220#comment-14041220 ] Sean Busbey commented on ACCUMULO-2938: --- alternatively, provide a configurable

[jira] [Commented] (ACCUMULO-2938) Investigate logging on KeyExtent to ensure no data leakage

2014-06-23 Thread Josh Elser (JIRA)
[ https://issues.apache.org/jira/browse/ACCUMULO-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041227#comment-14041227 ] Josh Elser commented on ACCUMULO-2938: -- That might be a nice middle ground. We

[jira] [Commented] (ACCUMULO-2938) Investigate logging on KeyExtent to ensure no data leakage

2014-06-23 Thread Christopher Tubbs (JIRA)
[ https://issues.apache.org/jira/browse/ACCUMULO-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041357#comment-14041357 ] Christopher Tubbs commented on ACCUMULO-2938: - Despite this issue being

[jira] [Commented] (ACCUMULO-2938) Investigate logging on KeyExtent to ensure no data leakage

2014-06-23 Thread Josh Elser (JIRA)
[ https://issues.apache.org/jira/browse/ACCUMULO-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041664#comment-14041664 ] Josh Elser commented on ACCUMULO-2938: -- Setting to 1.7.0 for triage. It's been in