logstash-input-jdbc 4.3.7 → 4.3.8
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 +5 -2
- data/docs/index.asciidoc +46 -45
- 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: c3b4aa32fb6fa7f58e176692944f94d913e54e4962b8432c70a92ee86cf7d8a1
|
4
|
+
data.tar.gz: dea81a0b3922e00b904ab0c217b8a5f07d35c253572cdfddc981fa1587c2f0a4
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 727274b3a33f09679d07e83cabe1eb3d6b6fb44970444c2f14ccd28d20dcc19fab8ed8abd93caa7cc32bf6a0fcc95434414e77712f23e2153c414074e2b31f2a
|
7
|
+
data.tar.gz: 9ceb91d5d9156b8cdc227cc4a0bfa56f3ff8db78a1e7d08c0be42f1616793f284a0b225d9e311ce4c5c3641550ab58614cca0eb6fc0c9e85f6afe7e1634a9e91
|
data/CHANGELOG.md
CHANGED
@@ -1,9 +1,12 @@
|
|
1
|
+
## 4.3.8
|
2
|
+
- [#273](https://github.com/logstash-plugins/logstash-input-jdbc/issues/273) Clarify use of use_column_value. Make last_run_metadata_path reference in record_last_run entry clickable.
|
3
|
+
|
1
4
|
## 4.3.7
|
2
|
-
- [#263](https://github.com/logstash-plugins/logstash-input-jdbc/issues/263) Load the driver with the system class loader. Fixes issue loading some JDBC drivers in Logstash 6.2+
|
5
|
+
- [#263](https://github.com/logstash-plugins/logstash-input-jdbc/issues/263) Load the driver with the system class loader. Fixes issue loading some JDBC drivers in Logstash 6.2+
|
3
6
|
|
4
7
|
## 4.3.6
|
5
8
|
- [#274](https://github.com/logstash-plugins/logstash-input-jdbc/issues/274) Fix regression with 4.3.5 that can result in NULL :sql_last_value depending on timestamp format
|
6
|
-
|
9
|
+
|
7
10
|
## 4.3.5
|
8
11
|
- [#140](https://github.com/logstash-plugins/logstash-input-jdbc/issues/140) Fix long standing bug where setting jdbc_default_timezone loses milliseconds. Force all usage of sql_last_value to be typed according to the settings.
|
9
12
|
|
data/docs/index.asciidoc
CHANGED
@@ -100,19 +100,19 @@ option is typically used when the SQL statement is large or cumbersome to supply
|
|
100
100
|
The file option only supports one SQL statement. The plugin will only accept one of the options.
|
101
101
|
It cannot read a statement from a file as well as from the `statement` configuration parameter.
|
102
102
|
|
103
|
-
==== Configuring multiple SQL statements
|
103
|
+
==== Configuring multiple SQL statements
|
104
104
|
|
105
|
-
Configuring multiple SQL statements is useful when there is a need to query and ingest data
|
106
|
-
from different database tables or views. It is possible to define separate Logstash
|
107
|
-
configuration files for each statement or to define multiple statements in a single configuration
|
108
|
-
file. When using multiple statements in a single Logstash configuration file, each statement
|
109
|
-
has to be defined as a separate jdbc input (including jdbc driver, connection string and other
|
110
|
-
required parameters).
|
105
|
+
Configuring multiple SQL statements is useful when there is a need to query and ingest data
|
106
|
+
from different database tables or views. It is possible to define separate Logstash
|
107
|
+
configuration files for each statement or to define multiple statements in a single configuration
|
108
|
+
file. When using multiple statements in a single Logstash configuration file, each statement
|
109
|
+
has to be defined as a separate jdbc input (including jdbc driver, connection string and other
|
110
|
+
required parameters).
|
111
111
|
|
112
|
-
Please note that if any of the statements use the `sql_last_value` parameter (e.g. for
|
113
|
-
ingesting only data changed since last run), each input should define its own
|
112
|
+
Please note that if any of the statements use the `sql_last_value` parameter (e.g. for
|
113
|
+
ingesting only data changed since last run), each input should define its own
|
114
114
|
`last_run_metadata_path` parameter. Failure to do so will result in undesired behaviour, as
|
115
|
-
all inputs will store their state to the same (default) metadata file, effectively
|
115
|
+
all inputs will store their state to the same (default) metadata file, effectively
|
116
116
|
overwriting each other's `sql_last_value`.
|
117
117
|
|
118
118
|
==== Predefined Parameters
|
@@ -185,7 +185,7 @@ input plugins.
|
|
185
185
|
|
186
186
|
|
187
187
|
[id="plugins-{type}s-{plugin}-clean_run"]
|
188
|
-
===== `clean_run`
|
188
|
+
===== `clean_run`
|
189
189
|
|
190
190
|
* Value type is <<boolean,boolean>>
|
191
191
|
* Default value is `false`
|
@@ -193,12 +193,12 @@ input plugins.
|
|
193
193
|
Whether the previous run state should be preserved
|
194
194
|
|
195
195
|
[id="plugins-{type}s-{plugin}-columns_charset"]
|
196
|
-
===== `columns_charset`
|
196
|
+
===== `columns_charset`
|
197
197
|
|
198
198
|
* Value type is <<hash,hash>>
|
199
199
|
* Default value is `{}`
|
200
200
|
|
201
|
-
The character encoding for specific columns. This option will override the `:charset` option
|
201
|
+
The character encoding for specific columns. This option will override the `:charset` option
|
202
202
|
for the specified columns.
|
203
203
|
|
204
204
|
Example:
|
@@ -215,7 +215,7 @@ input {
|
|
215
215
|
this will only convert column0 that has ISO-8859-1 as an original encoding.
|
216
216
|
|
217
217
|
[id="plugins-{type}s-{plugin}-connection_retry_attempts"]
|
218
|
-
===== `connection_retry_attempts`
|
218
|
+
===== `connection_retry_attempts`
|
219
219
|
|
220
220
|
* Value type is <<number,number>>
|
221
221
|
* Default value is `1`
|
@@ -223,7 +223,7 @@ this will only convert column0 that has ISO-8859-1 as an original encoding.
|
|
223
223
|
Maximum number of times to try connecting to database
|
224
224
|
|
225
225
|
[id="plugins-{type}s-{plugin}-connection_retry_attempts_wait_time"]
|
226
|
-
===== `connection_retry_attempts_wait_time`
|
226
|
+
===== `connection_retry_attempts_wait_time`
|
227
227
|
|
228
228
|
* Value type is <<number,number>>
|
229
229
|
* Default value is `0.5`
|
@@ -231,7 +231,7 @@ Maximum number of times to try connecting to database
|
|
231
231
|
Number of seconds to sleep between connection attempts
|
232
232
|
|
233
233
|
[id="plugins-{type}s-{plugin}-jdbc_connection_string"]
|
234
|
-
===== `jdbc_connection_string`
|
234
|
+
===== `jdbc_connection_string`
|
235
235
|
|
236
236
|
* This is a required setting.
|
237
237
|
* Value type is <<string,string>>
|
@@ -240,7 +240,7 @@ Number of seconds to sleep between connection attempts
|
|
240
240
|
JDBC connection string
|
241
241
|
|
242
242
|
[id="plugins-{type}s-{plugin}-jdbc_default_timezone"]
|
243
|
-
===== `jdbc_default_timezone`
|
243
|
+
===== `jdbc_default_timezone`
|
244
244
|
|
245
245
|
* Value type is <<string,string>>
|
246
246
|
* There is no default value for this setting.
|
@@ -254,7 +254,7 @@ of using the timezone setting of the local machine. You must use a canonical
|
|
254
254
|
timezone, *America/Denver*, for example.
|
255
255
|
|
256
256
|
[id="plugins-{type}s-{plugin}-jdbc_driver_class"]
|
257
|
-
===== `jdbc_driver_class`
|
257
|
+
===== `jdbc_driver_class`
|
258
258
|
|
259
259
|
* This is a required setting.
|
260
260
|
* Value type is <<string,string>>
|
@@ -265,7 +265,7 @@ NB per https://github.com/logstash-plugins/logstash-input-jdbc/issues/43 if you
|
|
265
265
|
the Oracle JDBC driver (ojdbc6.jar) the correct `jdbc_driver_class` is `"Java::oracle.jdbc.driver.OracleDriver"`
|
266
266
|
|
267
267
|
[id="plugins-{type}s-{plugin}-jdbc_driver_library"]
|
268
|
-
===== `jdbc_driver_library`
|
268
|
+
===== `jdbc_driver_library`
|
269
269
|
|
270
270
|
* Value type is <<string,string>>
|
271
271
|
* There is no default value for this setting.
|
@@ -280,7 +280,7 @@ required you can pass them separated by a comma.
|
|
280
280
|
If not provided, Plugin will look for the driver class in the Logstash Java classpath.
|
281
281
|
|
282
282
|
[id="plugins-{type}s-{plugin}-jdbc_fetch_size"]
|
283
|
-
===== `jdbc_fetch_size`
|
283
|
+
===== `jdbc_fetch_size`
|
284
284
|
|
285
285
|
* Value type is <<number,number>>
|
286
286
|
* There is no default value for this setting.
|
@@ -288,7 +288,7 @@ If not provided, Plugin will look for the driver class in the Logstash Java clas
|
|
288
288
|
JDBC fetch size. if not provided, respective driver's default will be used
|
289
289
|
|
290
290
|
[id="plugins-{type}s-{plugin}-jdbc_page_size"]
|
291
|
-
===== `jdbc_page_size`
|
291
|
+
===== `jdbc_page_size`
|
292
292
|
|
293
293
|
* Value type is <<number,number>>
|
294
294
|
* Default value is `100000`
|
@@ -296,7 +296,7 @@ JDBC fetch size. if not provided, respective driver's default will be used
|
|
296
296
|
JDBC page size
|
297
297
|
|
298
298
|
[id="plugins-{type}s-{plugin}-jdbc_paging_enabled"]
|
299
|
-
===== `jdbc_paging_enabled`
|
299
|
+
===== `jdbc_paging_enabled`
|
300
300
|
|
301
301
|
* Value type is <<boolean,boolean>>
|
302
302
|
* Default value is `false`
|
@@ -310,7 +310,7 @@ result-set. The limit size is set with `jdbc_page_size`.
|
|
310
310
|
Be aware that ordering is not guaranteed between queries.
|
311
311
|
|
312
312
|
[id="plugins-{type}s-{plugin}-jdbc_password"]
|
313
|
-
===== `jdbc_password`
|
313
|
+
===== `jdbc_password`
|
314
314
|
|
315
315
|
* Value type is <<password,password>>
|
316
316
|
* There is no default value for this setting.
|
@@ -318,7 +318,7 @@ Be aware that ordering is not guaranteed between queries.
|
|
318
318
|
JDBC password
|
319
319
|
|
320
320
|
[id="plugins-{type}s-{plugin}-jdbc_password_filepath"]
|
321
|
-
===== `jdbc_password_filepath`
|
321
|
+
===== `jdbc_password_filepath`
|
322
322
|
|
323
323
|
* Value type is <<path,path>>
|
324
324
|
* There is no default value for this setting.
|
@@ -326,7 +326,7 @@ JDBC password
|
|
326
326
|
JDBC password filename
|
327
327
|
|
328
328
|
[id="plugins-{type}s-{plugin}-jdbc_pool_timeout"]
|
329
|
-
===== `jdbc_pool_timeout`
|
329
|
+
===== `jdbc_pool_timeout`
|
330
330
|
|
331
331
|
* Value type is <<number,number>>
|
332
332
|
* Default value is `5`
|
@@ -335,7 +335,7 @@ Connection pool configuration.
|
|
335
335
|
The amount of seconds to wait to acquire a connection before raising a PoolTimeoutError (default 5)
|
336
336
|
|
337
337
|
[id="plugins-{type}s-{plugin}-jdbc_user"]
|
338
|
-
===== `jdbc_user`
|
338
|
+
===== `jdbc_user`
|
339
339
|
|
340
340
|
* This is a required setting.
|
341
341
|
* Value type is <<string,string>>
|
@@ -344,7 +344,7 @@ The amount of seconds to wait to acquire a connection before raising a PoolTimeo
|
|
344
344
|
JDBC user
|
345
345
|
|
346
346
|
[id="plugins-{type}s-{plugin}-jdbc_validate_connection"]
|
347
|
-
===== `jdbc_validate_connection`
|
347
|
+
===== `jdbc_validate_connection`
|
348
348
|
|
349
349
|
* Value type is <<boolean,boolean>>
|
350
350
|
* Default value is `false`
|
@@ -353,7 +353,7 @@ Connection pool configuration.
|
|
353
353
|
Validate connection before use.
|
354
354
|
|
355
355
|
[id="plugins-{type}s-{plugin}-jdbc_validation_timeout"]
|
356
|
-
===== `jdbc_validation_timeout`
|
356
|
+
===== `jdbc_validation_timeout`
|
357
357
|
|
358
358
|
* Value type is <<number,number>>
|
359
359
|
* Default value is `3600`
|
@@ -362,7 +362,7 @@ Connection pool configuration.
|
|
362
362
|
How often to validate a connection (in seconds)
|
363
363
|
|
364
364
|
[id="plugins-{type}s-{plugin}-last_run_metadata_path"]
|
365
|
-
===== `last_run_metadata_path`
|
365
|
+
===== `last_run_metadata_path`
|
366
366
|
|
367
367
|
* Value type is <<string,string>>
|
368
368
|
* Default value is `"/home/ph/.logstash_jdbc_last_run"`
|
@@ -370,7 +370,7 @@ How often to validate a connection (in seconds)
|
|
370
370
|
Path to file with last run time
|
371
371
|
|
372
372
|
[id="plugins-{type}s-{plugin}-lowercase_column_names"]
|
373
|
-
===== `lowercase_column_names`
|
373
|
+
===== `lowercase_column_names`
|
374
374
|
|
375
375
|
* Value type is <<boolean,boolean>>
|
376
376
|
* Default value is `true`
|
@@ -378,7 +378,7 @@ Path to file with last run time
|
|
378
378
|
Whether to force the lowercasing of identifier fields
|
379
379
|
|
380
380
|
[id="plugins-{type}s-{plugin}-parameters"]
|
381
|
-
===== `parameters`
|
381
|
+
===== `parameters`
|
382
382
|
|
383
383
|
* Value type is <<hash,hash>>
|
384
384
|
* Default value is `{}`
|
@@ -386,15 +386,15 @@ Whether to force the lowercasing of identifier fields
|
|
386
386
|
Hash of query parameter, for example `{ "target_id" => "321" }`
|
387
387
|
|
388
388
|
[id="plugins-{type}s-{plugin}-record_last_run"]
|
389
|
-
===== `record_last_run`
|
389
|
+
===== `record_last_run`
|
390
390
|
|
391
391
|
* Value type is <<boolean,boolean>>
|
392
392
|
* Default value is `true`
|
393
393
|
|
394
|
-
Whether to save state or not in last_run_metadata_path
|
394
|
+
Whether to save state or not in <<plugins-{type}s-{plugin}-last_run_metadata_path>>
|
395
395
|
|
396
396
|
[id="plugins-{type}s-{plugin}-schedule"]
|
397
|
-
===== `schedule`
|
397
|
+
===== `schedule`
|
398
398
|
|
399
399
|
* Value type is <<string,string>>
|
400
400
|
* There is no default value for this setting.
|
@@ -406,7 +406,7 @@ There is no schedule by default. If no schedule is given, then the statement is
|
|
406
406
|
exactly once.
|
407
407
|
|
408
408
|
[id="plugins-{type}s-{plugin}-sequel_opts"]
|
409
|
-
===== `sequel_opts`
|
409
|
+
===== `sequel_opts`
|
410
410
|
|
411
411
|
* Value type is <<hash,hash>>
|
412
412
|
* Default value is `{}`
|
@@ -420,7 +420,7 @@ examples of vendor-specific options can be found in this
|
|
420
420
|
documentation page: https://github.com/jeremyevans/sequel/blob/master/doc/opening_databases.rdoc
|
421
421
|
|
422
422
|
[id="plugins-{type}s-{plugin}-sql_log_level"]
|
423
|
-
===== `sql_log_level`
|
423
|
+
===== `sql_log_level`
|
424
424
|
|
425
425
|
* Value can be any of: `fatal`, `error`, `warn`, `info`, `debug`
|
426
426
|
* Default value is `"info"`
|
@@ -429,7 +429,7 @@ Log level at which to log SQL queries, the accepted values are the common ones f
|
|
429
429
|
info and debug. The default value is info.
|
430
430
|
|
431
431
|
[id="plugins-{type}s-{plugin}-statement"]
|
432
|
-
===== `statement`
|
432
|
+
===== `statement`
|
433
433
|
|
434
434
|
* Value type is <<string,string>>
|
435
435
|
* There is no default value for this setting.
|
@@ -449,7 +449,7 @@ here, ":target_id" is a named parameter. You can configure named parameters
|
|
449
449
|
with the `parameters` setting.
|
450
450
|
|
451
451
|
[id="plugins-{type}s-{plugin}-statement_filepath"]
|
452
|
-
===== `statement_filepath`
|
452
|
+
===== `statement_filepath`
|
453
453
|
|
454
454
|
* Value type is <<path,path>>
|
455
455
|
* There is no default value for this setting.
|
@@ -457,15 +457,15 @@ with the `parameters` setting.
|
|
457
457
|
Path of file containing statement to execute
|
458
458
|
|
459
459
|
[id="plugins-{type}s-{plugin}-tracking_column"]
|
460
|
-
===== `tracking_column`
|
460
|
+
===== `tracking_column`
|
461
461
|
|
462
462
|
* Value type is <<string,string>>
|
463
463
|
* There is no default value for this setting.
|
464
464
|
|
465
|
-
|
465
|
+
The column whose value is to be tracked if `use_column_value` is set to `true`
|
466
466
|
|
467
467
|
[id="plugins-{type}s-{plugin}-tracking_column_type"]
|
468
|
-
===== `tracking_column_type`
|
468
|
+
===== `tracking_column_type`
|
469
469
|
|
470
470
|
* Value can be any of: `numeric`, `timestamp`
|
471
471
|
* Default value is `"numeric"`
|
@@ -473,14 +473,15 @@ If tracking column value rather than timestamp, the column whose value is to be
|
|
473
473
|
Type of tracking column. Currently only "numeric" and "timestamp"
|
474
474
|
|
475
475
|
[id="plugins-{type}s-{plugin}-use_column_value"]
|
476
|
-
===== `use_column_value`
|
476
|
+
===== `use_column_value`
|
477
477
|
|
478
478
|
* Value type is <<boolean,boolean>>
|
479
479
|
* Default value is `false`
|
480
480
|
|
481
|
-
|
482
|
-
|
481
|
+
When set to `true`, uses the defined
|
482
|
+
<<plugins-{type}s-{plugin}-tracking_column>> value as the `:sql_last_value`. When set
|
483
|
+
to `false`, `:sql_last_value` reflects the last time the query was executed.
|
483
484
|
|
484
485
|
|
485
486
|
[id="plugins-{type}s-{plugin}-common-options"]
|
486
|
-
include::{include_path}/{type}.asciidoc[]
|
487
|
+
include::{include_path}/{type}.asciidoc[]
|
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.8'
|
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.8
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Elastic
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2018-
|
11
|
+
date: 2018-04-05 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|