[jira] [Commented] (KUDU-1868) Java client mishandles socket read timeouts for scans

2019-03-04 Thread Mike Percy (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783805#comment-16783805 ] Mike Percy commented on KUDU-1868: -- Merged as part of these patches from Will: *

[jira] [Commented] (KUDU-1868) Java client mishandles socket read timeouts for scans

2019-01-25 Thread Will Berkeley (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752770#comment-16752770 ] Will Berkeley commented on KUDU-1868: - I've done a good amount of investigation into this now. First

[jira] [Commented] (KUDU-1868) Java client mishandles socket read timeouts for scans

2019-01-25 Thread Will Berkeley (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752602#comment-16752602 ] Will Berkeley commented on KUDU-1868: - Sort of. The socket read timeout is a property of the

[jira] [Commented] (KUDU-1868) Java client mishandles socket read timeouts for scans

2019-01-25 Thread Grant Henke (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752595#comment-16752595 ] Grant Henke commented on KUDU-1868: --- Would it be reasonable to simply adjust the default to match the