[
https://issues.apache.org/jira/browse/FLUME-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635511#comment-13635511
]
Edward Sargisson commented on FLUME-1782:
-----------------------------------------
Hi Mike,
I've just taken a look at the new code based on your comment about not changing
the event. The effect of this is a breaking change to the
ElasticSearchEventSerializer interface so that the assigned timestamp can be
passed along. Unless we happen to have an alternative to the concern you raise
I think we're going to have to do that.
(I had been trying to avoid making changes to that interface - that's why
FLUME-1972 sets up a different interface. Maybe we should discuss joining those
interfaces?)
> 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-1.4.0-1.patch, FLUME-1782-1.4.0-2.patch,
> FLUME-1782-1.4.0.patch, 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
