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

Satoshi Iijima commented on FLUME-2207:
---------------------------------------

Hi,
Example is below. Please try it.

a1.sinks.k1.type = elasticsearch
a1.sinks.k1.indexNameBuilder.dateFormat = yyyy-MM-dd-HH
a1.sinks.k1.indexNameBuilder.timeZone = America/Los_Angeles
a1.sinks.k1.indexName = foo_index
a1.sinks.k1.indexType = bar_type
a1.sinks.k1.hostNames = 127.0.0.1:9200
a1.sinks.k1.channel = c1


> HDFS file suffix style index suffix in ElasticSearchSink
> --------------------------------------------------------
>
>                 Key: FLUME-2207
>                 URL: https://issues.apache.org/jira/browse/FLUME-2207
>             Project: Flume
>          Issue Type: Improvement
>          Components: Sinks+Sources
>    Affects Versions: v1.5.0
>            Reporter: Dib Ghosh
>             Fix For: v1.6.0
>
>         Attachments: FLUME-2207-1.patch
>
>
> Currently ElasticSearchSink indexName is appended with "YYYY-MM-DD" to 
> generate actual ElasticSearch index name and allow index rolling on a daily 
> basis. This works well for simpler use cases but is restrictive imho. User 
> should be able to add indexSuffix as per their own use case and also keep the 
> indexSuffix empty if requirement demands.
> agent.sinks.essink.indexName = flume becomes flume-2013-10-10.
> It will be really useful to have HDFS Sink filepath style  indexSuffix naming 
> i.e. "YYYY" will roll the indexes yearly, "YYYY-MM" will create indices 
> monthly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to