better handling for invalid driver paths #369
Comments
kares
added a commit
to kares/logstash-input-jdbc
that referenced
this issue
Jan 21, 2020
resolves logstash-plugins#369 (also related logstash-plugins#362)
This was referenced Jan 21, 2020
kares
added a commit
to logstash-plugins/logstash-integration-jdbc
that referenced
this issue
Jan 22, 2020
these are non-critical improvements for (input) driver loading. issues are kept on the original repo since they concern the plugin. this is expected to resolve logstash-plugins/logstash-input-jdbc#369 (also partially relates to logstash-plugins/logstash-input-jdbc#362)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
currently
jdbc_driver_pathloading is delayed until the first statement is executed,this means that if a plugin is using
schedulea failure in driver loading (such as insufficient read access) will not be visible in the plugin log but only in console.this is confusing esp. when using LS as a service (console not visible unless journald is inspected) - while LS is self contained its bringing in a driver.jar via this plugin and its not very clear permissions should be taken into account.
plugin should potentially document this + improve its driver.jar checking for read access ...
The text was updated successfully, but these errors were encountered: