[jira] [Updated] (FLUME-1782) Elastic Search sink does not use UTC to determine the correct index to write to.

["Edward Sargisson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward Sargisson updated FLUME-1782:
------------------------------------

    Attachment: FLUME-1782-1.4.0.patch

I have now updated and combined the patches. FLUME-1782-1.4.0.patch is now the only patch that should be applied to trunk. It contains the original fix to the defect as well as the user guide updates.

I have decided not to include the changes Israel Ekpo suggested. I don't believe I did them correctly and I think they are more confusing than useful. A developer who needs that functionality can use the patches in this work item to do that if required.
                
> 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.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