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

Wrappers for storing resources (filters, normalisers, etc...) on Elasticsearch #569

Closed
jnioche opened this Issue May 9, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@jnioche
Member

jnioche commented May 9, 2018

We store the resource files for the filters and normalisers alongside the code and into the uberjar, which works fine, but Elasticsearch users could store them into a specific index where they could be updated without having to rebuild the jar and restart the topology.

One option would be to have the content of the file in a stored text field but this means that you would not be able to push the file directly onto ES. Another approach is to use JSON documents for the resources, in which case users could send the resource files directly into the index.

@jnioche

This comment has been minimized.

Member

jnioche commented May 25, 2018

This could be extended to the parsefilter and urlfilter definitions themselves which are in JSON.

@jnioche

This comment has been minimized.

Member

jnioche commented May 30, 2018

See #577 for introduction of JSONResource interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment