You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fortunately, the Sequel gem already had the necessary functionality.
However, it turns out that Sequel _can_ do named timezones, but when you do
the date comes back as a DateTime object instead. As a result,
this should only use named_timezone support if defined, which should
save cycles for those who already have their date fields in UTC, rather
than punishing every user.
Use string date to test timezone conversion to guarantee similarity to the
issue case
Fixes#95
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
## 2.1.0
2
2
-[#85](https://github.com/logstash-plugins/logstash-input-jdbc/issues/85) make the jdbc_driver_library accept a list of elements separated by commas as in some situations we might need to load more than one jar/lib.
3
+
-[#89](https://github.com/logstash-plugins/logstash-input-jdbc/issues/89) Set application timezone for cases where time fields in data have no timezone.
3
4
4
5
## 2.0.5
5
6
-[#77](https://github.com/logstash-plugins/logstash-input-jdbc/issues/77) Time represented as RubyTime and not as Logstash::Timestamp
@@ -13,7 +14,7 @@
13
14
- Added catch-all configuration option for any other options that Sequel lib supports
14
15
15
16
## 2.0.0
16
-
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully,
17
+
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully,
17
18
instead of using Thread.raise on the plugins' threads. Ref: https://github.com/elastic/logstash/pull/3895
0 commit comments