JDBC Exception. No retry. {:exception=>#<NoMethodError: undefined method `start_with?' for 1:Fixnum>, :level=>:error}

[theangryangel]

JDBC Exception. No retry. {:exception=>#, :level=>:error}

from logstash-output-jdbc.

[theangryangel]

Can you give me the config you're running, if possible please Alex?

[alexschultz]

input {
couchdb_changes {
db => "couchDocumentDb"
host => "localhost"
username => "admin"
password => "password"
}
}

filter {
}

output {
if [doc][schema] == "special" {
jdbc {
idle_flush_time => 10
flush_size => 5
max_flush_exceptions => 5
username => "user"
password => "password"
connection_string => "jdbc:sqlserver://localhost:1433;databaseName=helloworld;"
statement => [ "INSERT INTO dbo.reports (ReportServer, ReportName, ReportPath, IsActive, CreatedBy, CreateDate, LastModifiedDate, IsAddParameter) VALUES(?, ?, ?, ?, ?, ?, ?, ?)",
"%{[doc][schema]}",
"%{[doc][schema]}",
"%{[doc][schema]}",
1,
"%{[doc][schema]}",
"%{[doc][schema]}",
"%{[doc][schema]}",
"%{[doc][schema]}",
1]
}
}
}

[theangryangel]

Just to see what happens, can you add quotes around the 1's in the statement array? I'm going to guess that it works. If that's the case I think I have a quick patch to write 😅

Edit: So something like:

statement => [ "INSERT INTO dbo.reports (ReportServer, ReportName, ReportPath, IsActive, CreatedBy, CreateDate, LastModifiedDate, IsAddParameter) VALUES(?, ?, ?, ?, ?, ?, ?, ?)",
"%{[doc][schema]}",
"%{[doc][schema]}",
"%{[doc][schema]}",
"1",
"%{[doc][schema]}",
"%{[doc][schema]}",
"%{[doc][schema]}",
"%{[doc][schema]}",
"1"]

[alexschultz]

Awesome, that fixed the initial issue! I have a couple of SQL syntax issues but I think those might be on my end.
Thanks for the super quick reply!

[theangryangel]

Thanks for being responsive! (seriously ❤️)

Honestly, it really shouldn't be error'ing like that, so I definitely have a patch to write and some test cases to add 👍

The SQL statement does have a mismatched number of ?'s and columns, so there is that as well.

[theangryangel]

I've backported this fix from the v5 branch to for v2 of logstash, and pushed 0.2.10 to rubygems 😄

You should find that this now works correctly, without throwing any errors

[alexschultz]

It's working now, thanks for the super quick turnaround!