-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RubyTime object is not Logstash::Timestamp #77
Labels
Comments
A temporary workaround: ruby {
code => "event['event_date'] = LogStash::Timestamp.new(event['event_date'])"
} |
Bad news Aaron, I'm getting an error with your workaround:
|
My apologies, I transcribed "LogStash::Timestamp.new" as "Logstash::Timestamp.new". When I capitalized the "S" your code worked. Thanks again. |
Excellent! I'll close this now. |
I meant your workaround code works. The jdbc input plugin is still indexing date fields as strings. |
Right. Oops 😄 |
This has been fixed in #83 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that the JDBC plugin is grabbing timestamps correctly, but it's only converting them to
RubyTime
objects, which is not the same thing as aLogstash::Timestamp
. This conversion should be possible without resorting to aruby{}
filter.See: https://discuss.elastic.co/t/logstash-date-filter-question/33663
The text was updated successfully, but these errors were encountered: