[jira] [Commented] (HADOOP-11526) Memory leak in Bzip2Compressor and Bzip2Decompressor

[ https://issues.apache.org/jira/browse/HADOOP-11526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358328#comment-14358328 ] Johannes Zillmann commented on HADOOP-11526: Question on the implications of

[jira] Commented: (HADOOP-6113) AccessControlException should display the full path

[ https://issues.apache.org/jira/browse/HADOOP-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964857#action_12964857 ] Johannes Zillmann commented on HADOOP-6113: --- one stacktrace example: {noformat}

[jira] Updated: (HADOOP-6934) test for ByteWritable comparator

[ https://issues.apache.org/jira/browse/HADOOP-6934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Zillmann updated HADOOP-6934: -- Status: Patch Available (was: Open) > test for ByteWritable comparator >

[jira] Updated: (HADOOP-6934) test for ByteWritable comparator

[ https://issues.apache.org/jira/browse/HADOOP-6934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Zillmann updated HADOOP-6934: -- Attachment: h-6934.patch Patch [^h-6934.patch] with the test attached. > test for Byt

[jira] Created: (HADOOP-6934) test for ByteWritable comparator

test for ByteWritable comparator Key: HADOOP-6934 URL: https://issues.apache.org/jira/browse/HADOOP-6934 Project: Hadoop Common Issue Type: Test Components: record Affects Versions: 0.21.0

[jira] Updated: (HADOOP-6928) Fix BooleanWritable comparator in 0.20

[ https://issues.apache.org/jira/browse/HADOOP-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Zillmann updated HADOOP-6928: -- Attachment: h-6928-2.patch added [^h-6928-2.patch] wich includes a test > Fix Boolean

[jira] Commented: (HADOOP-6797) DNS#getHosts() fallback leads to mix of network-interface addresse in case reverse lookup fails

[ https://issues.apache.org/jira/browse/HADOOP-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875116#action_12875116 ] Johannes Zillmann commented on HADOOP-6797: --- not sure if this could happen, but

[jira] Commented: (HADOOP-6797) DNS#getHosts() fallback leads to mix of network-interface addresse in case reverse lookup fails

[ https://issues.apache.org/jira/browse/HADOOP-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873963#action_12873963 ] Johannes Zillmann commented on HADOOP-6797: --- In case we would add or replace the

[jira] Created: (HADOOP-6797) DNS#getHosts() fallback leads to mix of network-interface addresse in case reverse lookup fails

DNS#getHosts() fallback leads to mix of network-interface addresse in case reverse lookup fails --- Key: HADOOP-6797 URL: https://issues.apache.org/jira/browse/HADOOP-6797

[jira] Commented: (HADOOP-6726) can't control maxRetries in case of SocketTimeoutException

[ https://issues.apache.org/jira/browse/HADOOP-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860883#action_12860883 ] Johannes Zillmann commented on HADOOP-6726: --- It would be fine if _ipc.client.con

[jira] Created: (HADOOP-6726) can't control maxRetries in case of SocketTimeoutException

can't control maxRetries in case of SocketTimeoutException -- Key: HADOOP-6726 URL: https://issues.apache.org/jira/browse/HADOOP-6726 Project: Hadoop Common Issue Type: Improvement