[
https://issues.apache.org/jira/browse/FLUME-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463436#comment-13463436
]
Hudson commented on FLUME-1600:
-------------------------------
Integrated in flume-trunk #309 (See
[https://builds.apache.org/job/flume-trunk/309/])
FLUME-1600. FileChannel metadata files should be written to a temp file and
then moved over existing files. (Revision
2c3b3116e685078fc742d3d3aa5f498a5c9c3b52)
Result = SUCCESS
hshreedharan :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=2c3b3116e685078fc742d3d3aa5f498a5c9c3b52
Files :
*
flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/LogFileV3.java
*
flume-ng-channels/flume-file-channel/src/test/java/org/apache/flume/channel/file/TestLogFile.java
> FileChannel metadata files should be written to a temp file and then moved
> over existing files
> ----------------------------------------------------------------------------------------------
>
> Key: FLUME-1600
> URL: https://issues.apache.org/jira/browse/FLUME-1600
> Project: Flume
> Issue Type: Improvement
> Components: Channel
> Affects Versions: v1.3.0
> Reporter: Brock Noland
> Assignee: Brock Noland
> Priority: Minor
> Attachments: FLUME-1600-0.patch
>
>
> Title says it all really. When we update the metadata we are actually
> truncating it and then writing out new metadata in it's place. We should
> write to a temp file instead.
--
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
