[
https://issues.apache.org/jira/browse/STORM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638754#comment-14638754
]
ASF GitHub Bot commented on STORM-960:
--------------------------------------
GitHub user dossett opened a pull request:
https://github.com/apache/storm/pull/653
STORM-960 HiveBolt should ack tuples only after flushing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dossett/storm HiveBoltAck
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/653.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #653
----
commit aac496ade94210888a0ca473df648855c408496b
Author: Sriharsha Chintalapani <[email protected]>
Date: 2015-07-21T22:42:22Z
STORM-951. Storm Hive connector leaking connections.
commit 6a5d0dcb44b58063035bfdaac4ebddba401dc914
Author: Aaron Dossett <[email protected]>
Date: 2015-07-23T12:50:25Z
STORM 960: HiveBolt should only ack after succesful flush
----
> Hive-Bolt can lose tuples when flushing data
> --------------------------------------------
>
> Key: STORM-960
> URL: https://issues.apache.org/jira/browse/STORM-960
> Project: Apache Storm
> Issue Type: Improvement
> Components: external
> Reporter: Aaron Dossett
> Priority: Minor
>
> In HiveBolt's execute method tuples are ack'd as they are received. When a
> batchsize of tuples has been received, the writers are flushed. However, if
> the flush fails only the most recent tuple will be marked as failed. All
> prior tuples will already have been ack'd. This creates a window for data
> loss.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
