From f7069258431ad3cd20430ed2879aeea702c951b6 Mon Sep 17 00:00:00 2001 From: Karen Metts Date: Wed, 5 Mar 2025 11:17:25 -0500 Subject: [PATCH 1/3] Doc: Fix formatting to prepare for migration --- docs/filter-jdbc_static.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/filter-jdbc_static.asciidoc b/docs/filter-jdbc_static.asciidoc index b91faec..c64367e 100644 --- a/docs/filter-jdbc_static.asciidoc +++ b/docs/filter-jdbc_static.asciidoc @@ -123,7 +123,7 @@ filter { add_field => { user_lastname => "%{[user][0][lastname]}" } remove_field => ["server", "user"] staging_directory => "/tmp/logstash/jdbc_static/import_data" - loader_schedule => "* */2 * * *" # run loaders every 2 hours + loader_schedule => "* */2 * * *" <8> jdbc_user => "logstash" jdbc_password => "example" jdbc_driver_class => "org.postgresql.Driver" @@ -153,6 +153,7 @@ returns multiple columns, the data is stored as a JSON object within the field. <6> When the user is not found in the database, an event is created using data from the <> `default hash` setting, and the event is tagged with the list set in <>. <7> Takes data from the JSON object and stores it in top-level event fields for easier analysis in Kibana. +<8> Runs loaders every 2 hours. Here's a full example: From 2270e085e970c2d01c83f7950c856129516350cc Mon Sep 17 00:00:00 2001 From: Karen Metts Date: Wed, 5 Mar 2025 11:28:33 -0500 Subject: [PATCH 2/3] Bump to v5.5.3 --- CHANGELOG.md | 3 +++ logstash-integration-jdbc.gemspec | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2d8b81e..2c80f96 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,6 @@ +## 5.5.3 + - 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) + ## 5.5.2 - 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) diff --git a/logstash-integration-jdbc.gemspec b/logstash-integration-jdbc.gemspec index 98c5a34..8986c5c 100755 --- a/logstash-integration-jdbc.gemspec +++ b/logstash-integration-jdbc.gemspec @@ -1,6 +1,6 @@ Gem::Specification.new do |s| s.name = 'logstash-integration-jdbc' - s.version = '5.5.2' + s.version = '5.5.3' s.licenses = ['Apache License (2.0)'] s.summary = "Integration with JDBC - input and filter plugins" 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" From e93223ed0629284728d82a8f98f9206f170f4dea Mon Sep 17 00:00:00 2001 From: Karen Metts <35154725+karenzone@users.noreply.github.com> Date: Wed, 5 Mar 2025 11:36:22 -0500 Subject: [PATCH 3/3] Update CHANGELOG.md with accurate description and link --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2c80f96..067b9f4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,5 @@ ## 5.5.3 - - 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) + - [DOC] Rework inline comment to a callout in preparation for upcoming MD conversion [#181](https://github.com/logstash-plugins/logstash-integration-jdbc/pull/181) ## 5.5.2 - 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)