You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/01/15 02:19:12 UTC

[jira] [Commented] (FLUME-1828) ResettableInputStream should support seek()

    [ https://issues.apache.org/jira/browse/FLUME-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553376#comment-13553376 ] 

Hudson commented on FLUME-1828:
-------------------------------

Integrated in flume-trunk #351 (See [https://builds.apache.org/job/flume-trunk/351/])
    FLUME-1828: ResettableInputStream should support seek() (Revision 70fe963ecab62bebab76b9f97fbeb312b1176f9f)

     Result = SUCCESS
brock : http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=70fe963ecab62bebab76b9f97fbeb312b1176f9f
Files : 
* flume-ng-core/src/main/java/org/apache/flume/serialization/ResettableInputStream.java
* flume-ng-core/src/test/java/org/apache/flume/serialization/ResettableTestStringInputStream.java
* flume-ng-core/src/main/java/org/apache/flume/serialization/ResettableFileInputStream.java
* flume-ng-core/src/test/java/org/apache/flume/serialization/TestResettableFileInputStream.java
* flume-ng-core/src/main/java/org/apache/flume/serialization/Seekable.java

                
> ResettableInputStream should support seek()
> -------------------------------------------
>
>                 Key: FLUME-1828
>                 URL: https://issues.apache.org/jira/browse/FLUME-1828
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Mike Percy
>            Assignee: Mike Percy
>             Fix For: v1.4.0
>
>         Attachments: FLUME-1828-0.patch, FLUME-1828-2.patch
>
>
> ResettableInputStream should support seek(). Without it, it's impossible to implement a performant Deserializer that has read-ahead capability. An example of a deserializer that needs read-ahead capability is a stack-trace deserializer.

--
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