logstash-input-jdbc 4.3.16 → 4.3.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +3 -0
- data/docs/index.asciidoc +12 -7
- data/logstash-input-jdbc.gemspec +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: fa9af10e83d8b696b96da4524bc03bcce28f6b2286f1f18f38e674c562cb2994
|
|
4
|
+
data.tar.gz: b824a04d01e52bd569cf34f14b2a77d8fb850bb05e3ae91f02a0823cc9e2be56
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 23bb34de4f7c363bac00b01899bf3cf40560e80c4b2456115bc3d27682a5e89a573b274be44daf9664a9b9c9558bc33a4ea23125d505d24cf275f60a241a4e60
|
|
7
|
+
data.tar.gz: 905bdf60952acfcae39f639b5d1183aa25359af3ffe4869a80dcacff6510301a316764d30eca8317f4face5e02d1e96ee3638040d2583defd40d7be6b3322c0d
|
data/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,6 @@
|
|
|
1
|
+
## 4.3.17
|
|
2
|
+
- Added documentation to provide more info about jdbc driver loading [#352](https://github.com/logstash-plugins/logstash-input-jdbc/pull/352)
|
|
3
|
+
|
|
1
4
|
## 4.3.16
|
|
2
5
|
- Add support for prepared statements [Issue 233](https://github.com/logstash-plugins/logstash-input-jdbc/issues/233)
|
|
3
6
|
|
data/docs/index.asciidoc
CHANGED
|
@@ -33,6 +33,9 @@ This plugin does not come packaged with JDBC driver libraries. The desired
|
|
|
33
33
|
jdbc driver library must be explicitly passed in to the plugin using the
|
|
34
34
|
`jdbc_driver_library` configuration option.
|
|
35
35
|
|
|
36
|
+
See the <<plugins-{type}s-{plugin}-jdbc_driver_library>> and <<plugins-{type}s-{plugin}-jdbc_driver_class>>
|
|
37
|
+
options for more info.
|
|
38
|
+
|
|
36
39
|
==== Scheduling
|
|
37
40
|
|
|
38
41
|
Input from this plugin can be scheduled to run periodically according to a specific
|
|
@@ -317,8 +320,12 @@ database timezone is UTC then you do not need to set either of these settings.
|
|
|
317
320
|
* There is no default value for this setting.
|
|
318
321
|
|
|
319
322
|
JDBC driver class to load, for example, "org.apache.derby.jdbc.ClientDriver"
|
|
320
|
-
|
|
321
|
-
|
|
323
|
+
|
|
324
|
+
NOTE: Per https://github.com/logstash-plugins/logstash-input-jdbc/issues/43, prepending `Java::` to the driver class
|
|
325
|
+
may be required if it appears that the driver is not being loaded correctly despite relevant jar(s) being provided by
|
|
326
|
+
either via the `jdbc_driver_library` setting or being placed in the Logstash Java classpath. This is known to be the
|
|
327
|
+
case for the Oracle JDBC driver (ojdbc6.jar), where the correct `jdbc_driver_class` is
|
|
328
|
+
`"Java::oracle.jdbc.driver.OracleDriver"`, and may also be the case for other JDBC drivers.
|
|
322
329
|
|
|
323
330
|
[id="plugins-{type}s-{plugin}-jdbc_driver_library"]
|
|
324
331
|
===== `jdbc_driver_library`
|
|
@@ -326,14 +333,12 @@ the Oracle JDBC driver (ojdbc6.jar) the correct `jdbc_driver_class` is `"Java::o
|
|
|
326
333
|
* Value type is <<string,string>>
|
|
327
334
|
* There is no default value for this setting.
|
|
328
335
|
|
|
329
|
-
Tentative of abstracting JDBC logic to a mixin
|
|
330
|
-
for potential reuse in other plugins (input/output)
|
|
331
|
-
This method is called when someone includes this module
|
|
332
|
-
Add these methods to the 'base' given.
|
|
333
336
|
JDBC driver library path to third party driver library. In case of multiple libraries being
|
|
334
337
|
required you can pass them separated by a comma.
|
|
335
338
|
|
|
336
|
-
If not provided, Plugin will look for the driver class in the Logstash Java classpath.
|
|
339
|
+
NOTE: If not provided, Plugin will look for the driver class in the Logstash Java classpath. Additionally, if the library
|
|
340
|
+
does not appear to be being loaded correctly via this setting, placing the relevant jar(s) in the Logstash Java
|
|
341
|
+
classpath rather than via this setting may help.
|
|
337
342
|
|
|
338
343
|
[id="plugins-{type}s-{plugin}-jdbc_fetch_size"]
|
|
339
344
|
===== `jdbc_fetch_size`
|
data/logstash-input-jdbc.gemspec
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Gem::Specification.new do |s|
|
|
2
2
|
s.name = 'logstash-input-jdbc'
|
|
3
|
-
s.version = '4.3.
|
|
3
|
+
s.version = '4.3.17'
|
|
4
4
|
s.licenses = ['Apache License (2.0)']
|
|
5
5
|
s.summary = "Creates events from JDBC data"
|
|
6
6
|
s.description = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: logstash-input-jdbc
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 4.3.
|
|
4
|
+
version: 4.3.17
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Elastic
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2019-
|
|
11
|
+
date: 2019-10-22 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|