logstash-integration-jdbc 5.5.2 → 5.5.3

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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 837344b940ff8c7af09a52e7947507aa2431a39feb3562241218bdcdb03b0ae8
4
- data.tar.gz: dd89db28ba9ab3ee55d57164d5117dde658f18cb534e0bebec2d357fece044a2
3
+ metadata.gz: a28e2a3a37342bc631ed300da7fa687e99fc879d8cc599669d64e2cfc6418177
4
+ data.tar.gz: 38b675462f29af81148dbdcc58144a2e3df932b6c6a44825b580a3468ac90acb
5
5
  SHA512:
6
- metadata.gz: 5b6bba9b8ad12d504755f60409461236a0b42ae52f91a5503fcd8fa18c4c0ea7d9e900a13d917d3ade818c4332a2cd06e2c1fcf56d34cbe1604712a87b364414
7
- data.tar.gz: 5ccb895bdcca3602e93ab9c27f2032131ed71ec763fb77b95dee4ea552d8ec8be695573e997d63875b33e907a94035ec3e01101e69b722a315ff0f5613f18d62
6
+ metadata.gz: b3af9d1d0c7ddc88b8102d7fafb96a9c379a734266698a3136e9e9522f640f64f4f019ea5820c9bc382a460df5f47f2fc62bb6cf8c3ad47ad84f5069710831cd
7
+ data.tar.gz: 41a6e399b350068d1ed337c158b94f9457f0ace2f31588888db8c99b9e20a39f7fe0f06ab4e809cd01c7a635c9ede2a00629aa1ecf04b9cd86951fdda5c9a828
data/CHANGELOG.md CHANGED
@@ -1,3 +1,6 @@
1
+ ## 5.5.3
2
+ - [DOC] Rework inline comment to a callout in preparation for upcoming MD conversion [#181](https://github.com/logstash-plugins/logstash-integration-jdbc/pull/181)
3
+
1
4
  ## 5.5.2
2
5
  - FIX: the input plugin's prior behaviour of opening a new database connection for each scheduled run (removed in `v5.4.1`) is restored, ensuring that infrequently-run schedules do not hold open connections to their databases indefinitely, _without_ reintroducing the leak [#130](https://github.com/logstash-plugins/logstash-integration-jdbc/pull/130)
3
6
 
@@ -123,7 +123,7 @@ filter {
123
123
  add_field => { user_lastname => "%{[user][0][lastname]}" }
124
124
  remove_field => ["server", "user"]
125
125
  staging_directory => "/tmp/logstash/jdbc_static/import_data"
126
- loader_schedule => "* */2 * * *" # run loaders every 2 hours
126
+ loader_schedule => "* */2 * * *" <8>
127
127
  jdbc_user => "logstash"
128
128
  jdbc_password => "example"
129
129
  jdbc_driver_class => "org.postgresql.Driver"
@@ -153,6 +153,7 @@ returns multiple columns, the data is stored as a JSON object within the field.
153
153
  <6> When the user is not found in the database, an event is created using data from the <<plugins-{type}s-{plugin}-local_lookups>> `default hash` setting, and the event is tagged with the list set in <<plugins-{type}s-{plugin}-tag_on_default_use>>.
154
154
  <7> Takes data from the JSON object and stores it in top-level event fields for
155
155
  easier analysis in Kibana.
156
+ <8> Runs loaders every 2 hours.
156
157
 
157
158
  Here's a full example:
158
159
 
@@ -1,6 +1,6 @@
1
1
  Gem::Specification.new do |s|
2
2
  s.name = 'logstash-integration-jdbc'
3
- s.version = '5.5.2'
3
+ s.version = '5.5.3'
4
4
  s.licenses = ['Apache License (2.0)']
5
5
  s.summary = "Integration with JDBC - input and filter plugins"
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-integration-jdbc
3
3
  version: !ruby/object:Gem::Version
4
- version: 5.5.2
4
+ version: 5.5.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Elastic
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-12-23 00:00:00.000000000 Z
11
+ date: 2025-03-07 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  requirement: !ruby/object:Gem::Requirement