[
https://issues.apache.org/jira/browse/FLUME-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604310#comment-13604310
]
Israel Ekpo commented on FLUME-1782:
------------------------------------
Hi Edward,
I was not stating that it is the wisest thing to do.
I just think it will be a good idea to be flexible with the timezones so that
in the future if you need to use a different timezone other than UTC, it will
just be a matter of changing the value.
This can make future customization for other use cases easier.
You can set UTC as the default timzeone but allow the option to set it to other
ones if the uses wishes to do so.
> Elastic Search sink does not use UTC to determine the correct index to write
> to.
> --------------------------------------------------------------------------------
>
> Key: FLUME-1782
> URL: https://issues.apache.org/jira/browse/FLUME-1782
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Reporter: Edward Sargisson
> Fix For: v1.4.0
>
> Attachments: flume-1782-2.patch, flume-1782-3.patch, flume-1782.patch
>
>
> The GUI for logs in ElasticSearch, Kibana, uses the utc date to determine
> which index to read for a search. The Flume ElasticSearch sink is using the
> local timezone to determine which index to write to. This means that events
> are being placed in the incorrect index and Kibana doesn't always find them.
--
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
