I am getting this exception when getting my data with the JDBC plugin:
error:
26413962
Sequel::InvalidValue
TZInfo::AmbiguousTime: 2017-11-05T01:30:00+00:00 is an ambiguous local time.
This is probably because I am already converting my timezone in my JDBC plugin with this parameter:
jdbc_default_timezone => "America/New_York"
Therefore 1:30am happened twice on November 5th, and I suspect Logstash doesn't know what to do and it fall in an infinite loop.
As a workaround, I removed the jdbc_default_timezone parameter and instead I convert my values in UTC in the select statement, like this:
DATEADD(hh, DATEDIFF(hh, GETDATE(), GETUTCDATE()), th.[DueDate]) as DueDate
But this workaround is annoying since I need to modify all of my logstash inputs date columns.
Is there a way to force it to pick any of the two possible times, or any other way?
Thanks.