Skip to content
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

DATE column type not supported #17

Open
cm226 opened this issue Feb 18, 2024 · 0 comments · May be fixed by #18
Open

DATE column type not supported #17

cm226 opened this issue Feb 18, 2024 · 0 comments · May be fixed by #18
Labels

Comments

@cm226
Copy link

cm226 commented Feb 18, 2024

Logstash information:

Please include the following information:

  1. Logstash version

Using bundled JDK: /usr/share/logstash/jdk
logstash 8.12.1

Steps to reproduce:
Use the logstash input sqlLit plugin on a table with a DATE column

I used this plugin on a table with a DATE column type. It looks like the date column gets converted to a ruby date type and is passed on to logstash, which then doesn't know what to do with it.

Provide logs (if relevant):
The log message you get is this one:
Error: Missing Converter handling for full class name=org.jruby.gen.RubyObject31, simple name=RubyObject31

I tried to fix using the remove_field mutator, but it didn't seem to fix the issue, I'm not sure if the error is being generated before the mutator is being run?

I managed to fix it by adding

if element.instance_of? Date
                event.set(column.to_s, element.to_s)

To the plugin, I don't know much about ruby so there might be a better way. Ill raise a PR, in case this helps anybody else with the same issue.

@cm226 cm226 added the bug label Feb 18, 2024
@cm226 cm226 linked a pull request Feb 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant