logstash-output-vespa_feed 0.2.0 → 0.4.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +12 -3
- data/VERSION +1 -1
- data/docs/index.asciidoc +8 -2
- data/lib/logstash-output-vespa_feed_jars.rb +1 -1
- data/vendor/jar-dependencies/org/logstashplugins/logstash-output-vespa_feed/{0.2.0/logstash-output-vespa_feed-0.2.0.jar → 0.4.0/logstash-output-vespa_feed-0.4.0.jar} +0 -0
- metadata +3 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: f560b57ecd2a25e2a50a6640a90c9803077474b090fe1d539c24cf2cdabc362e
|
4
|
+
data.tar.gz: 25ca7fa19e63fc3863f7c9576dcdaa4b1c7a74dbecd1758c5f2e455414e396c6
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: ba80b8fcab865ea83e71a1d9e75c782335991001be58c08cc51756ce1c4488c6810501f35f5a504ae7fdf5a740512bbf74978b61ce31f555a543339ab2ab4292
|
7
|
+
data.tar.gz: 1aacfe2d3ed631bd471669d4c3fe175bec2eb676ad9a90931b55115c8b9d795fe1a7bad0edf90dbefdff2aa0fca04495535ba86462a8a49409b6a6dfe3e2eb4a
|
data/README.md
CHANGED
@@ -6,7 +6,7 @@ Plugin for [Logstash](https://github.com/elastic/logstash) to write to [Vespa](h
|
|
6
6
|
|
7
7
|
Download and unpack/install Logstash, then:
|
8
8
|
```
|
9
|
-
bin/logstash-plugin install logstash-output-
|
9
|
+
bin/logstash-plugin install logstash-output-vespa_feed
|
10
10
|
```
|
11
11
|
|
12
12
|
## Development
|
@@ -15,11 +15,18 @@ If you're developing the plugin, you'll want to do something like:
|
|
15
15
|
# build the gem
|
16
16
|
./gradlew gem
|
17
17
|
# install it as a Logstash plugin
|
18
|
-
/opt/logstash/bin/logstash-plugin install /path/to/logstash-output-vespa/logstash-output-
|
18
|
+
/opt/logstash/bin/logstash-plugin install /path/to/logstash-output-vespa/logstash-output-vespa_feed-0.3.0.gem
|
19
19
|
# profit
|
20
20
|
/opt/logstash/bin/logstash
|
21
21
|
```
|
22
|
-
Some more good info can be found [here](https://www.elastic.co/guide/en/logstash/current/java-output-plugin.html).
|
22
|
+
Some more good info about Logstash Java plugins can be found [here](https://www.elastic.co/guide/en/logstash/current/java-output-plugin.html).
|
23
|
+
|
24
|
+
It looks like the JVM options from [here](https://github.com/logstash-plugins/.ci/blob/main/dockerjdk17.env)
|
25
|
+
are useful to make JRuby's `bundle install` work.
|
26
|
+
|
27
|
+
Note to self: for some reason, `bundle exec rake publish_gem` fails, but `gem push logstash-output-vespa_feed-$VERSION.gem`
|
28
|
+
does the trick.
|
29
|
+
|
23
30
|
## Usage
|
24
31
|
|
25
32
|
Logstash config example:
|
@@ -69,7 +76,9 @@ output {
|
|
69
76
|
|
70
77
|
# Vespa endpoint, namespace, doc type (from the schema)
|
71
78
|
vespa_url => "http://localhost:8080"
|
79
|
+
# namespace could be static or in the %{field} format, picking from a field in the document
|
72
80
|
namespace => "no_default_provide_yours"
|
81
|
+
# similarly, doc type could be static or in the %{field} format
|
73
82
|
document_type => "no_default_provide_yours_from_schema"
|
74
83
|
|
75
84
|
# take the document ID from this field in each row
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.
|
1
|
+
0.4.0
|
data/docs/index.asciidoc
CHANGED
@@ -58,14 +58,20 @@ URL to the Vespa instance
|
|
58
58
|
|
59
59
|
* Value type is <<string,string>>
|
60
60
|
|
61
|
-
Vespa namespace. A logical grouping of documents in Vespa
|
61
|
+
Vespa namespace. A logical grouping of documents in Vespa.
|
62
|
+
|
63
|
+
Can be static or dynamic, i.e. you can use something like `%{foo}` to use the value in the `foo` field as the namespace. If the field is not present or returns null, the plugin will use the field name as is (here, `foo`).
|
62
64
|
|
63
65
|
[id="plugins-{type}s-{plugin}-document_type"]
|
64
66
|
===== `document_type`
|
65
67
|
|
66
68
|
* Value type is <<string,string>>
|
67
69
|
|
68
|
-
Document type.
|
70
|
+
Document type. Physical separation of documents in different files underneath.
|
71
|
+
|
72
|
+
You should see it in the Vespa services.xml file as well as in the schema file.
|
73
|
+
|
74
|
+
Like `namespace`, this can be static or dynamic. So you can use `%{foo}` to use the value in the `foo` field as the document type. If the field is not present or returns null, the plugin will use the field name as is (here, `foo`).
|
69
75
|
|
70
76
|
[id="plugins-{type}s-{plugin}-id_field"]
|
71
77
|
===== `id_field`
|
Binary file
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: logstash-output-vespa_feed
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.4.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Radu Gheorghe
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2024-
|
11
|
+
date: 2024-08-26 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|
@@ -77,7 +77,7 @@ files:
|
|
77
77
|
- lib/logstash-output-vespa_feed_jars.rb
|
78
78
|
- lib/logstash/outputs/vespa_feed.rb
|
79
79
|
- logstash-output-vespa_feed.gemspec
|
80
|
-
- vendor/jar-dependencies/org/logstashplugins/logstash-output-vespa_feed/0.
|
80
|
+
- vendor/jar-dependencies/org/logstashplugins/logstash-output-vespa_feed/0.4.0/logstash-output-vespa_feed-0.4.0.jar
|
81
81
|
homepage: https://vespa.ai
|
82
82
|
licenses:
|
83
83
|
- Apache-2.0
|