Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for kv in Ingest Node #22222

Closed
fhopf opened this issue Dec 16, 2016 · 3 comments
Closed

Support for kv in Ingest Node #22222

fhopf opened this issue Dec 16, 2016 · 3 comments
Assignees
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement

Comments

@fhopf
Copy link
Contributor

fhopf commented Dec 16, 2016

Describe the feature:

It would be very nice to have ingest node support similar to the kv filter in Logstash https://www.elastic.co/guide/en/logstash/current/plugins-filters-kv.html

It is mentioned in the original ingest node issue #14049 but implementation never seems to have happened. Are there any plans for support in the future?

@clintongormley clintongormley added :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement labels Dec 16, 2016
@clintongormley
Copy link

@talevy any reason the kv processor was left out?

@talevy
Copy link
Contributor

talevy commented Dec 16, 2016

@clintongormley no super strong reason, due to where we were at the time it was punted to v2 status.

I can work on this and get it in for 5.2

@talevy talevy self-assigned this Dec 16, 2016
@spinscale
Copy link
Contributor

@fhopf a very poor man's kv filter in between could be done using the script processor, like done here, however this requires script.painless.regex.enabled=true and will be much cleaner/less error prone in a real processor, that does not make use of regexes, so handle with care. Looking forward to the real thing :-)

talevy added a commit to talevy/elasticsearch that referenced this issue Dec 20, 2016
Now you can parse field values of the `key=value` variety and have
`key` be inserted as a field name in an ingest document.

Closes elastic#22222.
talevy added a commit that referenced this issue Dec 20, 2016
Now you can parse field values of the `key=value` variety and have
`key` be inserted as a field name in an ingest document.

Closes #22222.
talevy added a commit that referenced this issue Dec 20, 2016
Now you can parse field values of the `key=value` variety and have
`key` be inserted as a field name in an ingest document.

Closes #22222.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement
Projects
None yet
Development

No branches or pull requests

4 participants