Open endersonmaia opened 7 years ago
I tryied to replicate the error, and created a new table with some fields and a smalldatetime one, but couldn't replicate the error.
I simplifyied the setup and tested with my actual database, and the error is not showing.
I got to the conclusion the error was with a smalldatetime field, 'cause when I remove this field from the query, I get the error.
I'll try some more different setups to see if I can replicate it.
If I can't replicate, I'll try to show my actual setup (it's big queries and messy, that's why I'm avoiding showing it here).
Close this issue, I couldn't replicate it! Sorry!
We do have an outstanding issue with JDBC type plugins that try to add a Date datatype instance to an event which we do not currently support. The Java based Event feature needs to be able to seamlessly convert Ruby datatypes to their equivalent Java datatype and back again losslessly.
I need to modify the code to check for any date or datetime objects and safely convert them.
I am leaving this issue open for a while for others benefit.
We do have an outstanding issue with JDBC type plugins
Since you mentioned this, I noticed an inconssistant behavior between input-jdbc
and filter-jdbc_streaming
around SQL Server numeric
data type.
I presume this could be related to this convertions of data types, right ?
When I use a SQL query with some
smalldatetime
field, I get this error :