logstash-filter-jdbc_static 1.0.5 → 1.0.6
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 +18 -3
- data/logstash-filter-jdbc_static.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: d3b81e0c9308bdc5e2ed77ff83285478e1acb576014a87066b9515463556054a
|
|
4
|
+
data.tar.gz: 9b7712e0be06ba5bf6aba7faea67eb241b70597378b0348dcc75ae114fe6e9ba
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 27e86d778e71192f76c2e205907fd2f846aced383f35cd3df85e4ff6b191d66d68c7395c6195668ae003813f5bf020110f5528f9c8274c476984a476655a691c
|
|
7
|
+
data.tar.gz: '0091f4a6ffa0082ed1b95e287b502fcbf765c14e6f8400c5dc4a9782825d9603a465058f9ac86cb59c75bba0bf601beb1d0f300d397d4825f17fcd9a4761a4cb'
|
data/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,6 @@
|
|
|
1
|
+
## 1.0.6
|
|
2
|
+
- Added info to documentation to emphasize significance of table order [36](https://github.com/logstash-plugins/logstash-filter-jdbc_static/pull/36)
|
|
3
|
+
|
|
1
4
|
## 1.0.5
|
|
2
5
|
- Fixed issue where overly restrictive dependency on rufus scheduler was stopping Logstash from upgrading this plugin. [35](https://github.com/logstash-plugins/logstash-filter-jdbc_static/pull/35)
|
|
3
6
|
|
data/docs/index.asciidoc
CHANGED
|
@@ -54,11 +54,11 @@ database connection.
|
|
|
54
54
|
*lookups*::
|
|
55
55
|
|
|
56
56
|
Perform lookup queries on the local database to enrich the events.
|
|
57
|
-
Define as many lookups as needed to
|
|
57
|
+
Define as many lookups as needed to enrich the event from all
|
|
58
58
|
lookup tables in one pass. Ideally the SQL statement should only
|
|
59
59
|
return one row. Any rows are converted to Hash objects and are
|
|
60
60
|
stored in a target field that is an Array.
|
|
61
|
-
|
|
61
|
+
+
|
|
62
62
|
The following example config fetches data from a remote database, caches it in a
|
|
63
63
|
local database, and uses lookups to enrich events with data cached in the local
|
|
64
64
|
database.
|
|
@@ -131,6 +131,8 @@ filter {
|
|
|
131
131
|
locally.
|
|
132
132
|
<2> Defines the columns, types, and indexes used to build the local database
|
|
133
133
|
structure. The column names and types should match the external database.
|
|
134
|
+
The order of table definitions is significant and should match that of the loader queries.
|
|
135
|
+
See <<plugins-{type}s-{plugin}-object_order>>.
|
|
134
136
|
<3> Performs lookup queries on the local database to enrich the events.
|
|
135
137
|
<4> Specifies the event field that will store the looked-up data. If the lookup
|
|
136
138
|
returns multiple columns, the data is stored as a JSON object within the field.
|
|
@@ -246,6 +248,19 @@ However, after setting up the filter, you should watch the lookup results and
|
|
|
246
248
|
view the logs to verify correct operation.
|
|
247
249
|
===============================
|
|
248
250
|
|
|
251
|
+
[id="plugins-{type}s-{plugin}-object_order"]
|
|
252
|
+
==== Loader column and local_db_object order dependency
|
|
253
|
+
|
|
254
|
+
[IMPORTANT]
|
|
255
|
+
===============================
|
|
256
|
+
For loader performance reasons, the loading mechanism uses a CSV style file with an inbuilt
|
|
257
|
+
Derby file import procedure to add the remote data to the local db. The retrieved columns
|
|
258
|
+
are written to the CSV file as is and the file import procedure expects a 1 to 1 correspondence
|
|
259
|
+
to the order of the columns specified in the local_db_object settings. Please ensure that this
|
|
260
|
+
order is in place.
|
|
261
|
+
===============================
|
|
262
|
+
|
|
263
|
+
|
|
249
264
|
[id="plugins-{type}s-{plugin}-options"]
|
|
250
265
|
==== Jdbc_static Filter Configuration Options
|
|
251
266
|
|
|
@@ -507,7 +522,7 @@ must read the important multiple pipeline notice at the top of the page.
|
|
|
507
522
|
* Default value is `[]`
|
|
508
523
|
|
|
509
524
|
The array should contain one or more Hashes. Each Hash represents a lookup
|
|
510
|
-
|
|
525
|
+
enrichment. Each Hash is validated according to the table below.
|
|
511
526
|
|
|
512
527
|
[cols="<,<,<",options="header",]
|
|
513
528
|
|=======================================================================
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Gem::Specification.new do |s|
|
|
2
2
|
s.name = 'logstash-filter-jdbc_static'
|
|
3
|
-
s.version = '1.0.
|
|
3
|
+
s.version = '1.0.6'
|
|
4
4
|
s.licenses = ['Apache-2.0']
|
|
5
5
|
s.summary = "This filter executes a SQL query to fetch a SQL query result, store it locally then use a second SQL query to update an event."
|
|
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-filter-jdbc_static
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.0.
|
|
4
|
+
version: 1.0.6
|
|
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-10-29 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|