[ https://issues.apache.org/jira/browse/STORM-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941793#comment-14941793 ]
ASF GitHub Bot commented on STORM-1079: --------------------------------------- Github user Parth-Brahmbhatt commented on the pull request: https://github.com/apache/storm/pull/772#issuecomment-145159356 why would tuples start to timeout given before the tuple timeout occurs we have a tick tuple that fires and tries to flush the batch even if it has not reached the desired size? I thought the only difference the users would see now is that their latency may go up in a low throughput system unless they explicitly set the batch size = 1. > Batch Puts to HBase > ------------------- > > Key: STORM-1079 > URL: https://issues.apache.org/jira/browse/STORM-1079 > Project: Apache Storm > Issue Type: Improvement > Components: storm-hbase > Reporter: Sriharsha Chintalapani > Assignee: Sriharsha Chintalapani > Fix For: 0.11.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)