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

Hudson commented on FLUME-881:
------------------------------

Integrated in flume-trunk #145 (See 
[https://builds.apache.org/job/flume-trunk/145/])
    FLUME-881. HDFS Sink to select writableFormat based on file type.

(Jarek Jarcec Cecho via Arvind Prabhakar) (Revision 1305207)

     Result = SUCCESS
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1305207
Files : 
* 
/incubator/flume/trunk/flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/HDFSEventSink.java

                
> Would be nice if HDFS Sink would automatically choose best writableFormat 
> based on fileType
> -------------------------------------------------------------------------------------------
>
>                 Key: FLUME-881
>                 URL: https://issues.apache.org/jira/browse/FLUME-881
>             Project: Flume
>          Issue Type: Improvement
>          Components: Sinks+Sources
>    Affects Versions: v1.0.0, v1.1.0
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>            Priority: Minor
>             Fix For: v1.2.0
>
>         Attachments: FLUME-881.patch
>
>
> Currently user can specify both file type (SequenceFile, DataStream, ...) and 
> writable format (Text ~ append new line character, Writable ~ serialize as 
> is) of HDFS sink output file. Both properties have default values, however 
> when user redefine only file type to DataStream, flume will still use default 
> Writable writable format that will not append separate serialized events with 
> new line character. 
> Would be nice if flume would choose default value of writable format based on 
> current file type, so that for example for DataStream file type, default 
> writable format would be Text instead of Writable. I believe that would lead 
> to less confused users.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to