[
https://issues.apache.org/jira/browse/FLUME-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456284#comment-13456284
]
Hudson commented on FLUME-1583:
-------------------------------
Integrated in flume-trunk #304 (See
[https://builds.apache.org/job/flume-trunk/304/])
FLUME-1583. FileChannel fast full replay will always be used if enabled
(Revision f54148a3f53e5c53bc3932b208f25373d3c6ccbb)
Result = SUCCESS
hshreedharan :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=f54148a3f53e5c53bc3932b208f25373d3c6ccbb
Files :
*
flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/CheckpointRebuilder.java
*
flume-ng-channels/flume-file-channel/src/test/java/org/apache/flume/channel/file/TestCheckpointRebuilder.java
*
flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/ReplayHandler.java
*
flume-ng-channels/flume-file-channel/src/test/java/org/apache/flume/channel/file/TestFileChannelRestart.java
*
flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/Log.java
*
flume-ng-channels/flume-file-channel/src/test/java/org/apache/flume/channel/file/TestUtils.java
> FileChannel fast full replay will always be used if enabled
> -----------------------------------------------------------
>
> Key: FLUME-1583
> URL: https://issues.apache.org/jira/browse/FLUME-1583
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Reporter: Brock Noland
> Assignee: Brock Noland
> Fix For: v1.3.0
>
> Attachments: FLUME-1583-1.patch, FLUME-1583-2.patch
>
>
> If enabled, fast full replay will always be used. The reason is in Log.replay
> passed the full path to the checkpoint file it ReplayHandler. ReplayHandler
> then passes the this to CheckpointBuilder. Checkpoint builder tacks on
> "checkpoint" as if it was a directory and then check it's existence. It will
> never exist and as such fast replay will take place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
