For example the following paragraph:
This filter works by fetching data from a remote database, caching it in a local, in-memory Apache Derby database, and using lookups to enrich events with data cached in the local database. You can set up the filter to load the remote data once (for static data), or you can schedule remote loading to run periodically (for data that needs to be refreshed).
could be extended by:
Please note that Apache Derby might not support the entire SQL syntax and feature-set of your backend/source/remote database. Features likeLIMITor bitwise operators (<<and>>) are not available when using this filter plugin.
Given issues like https://github.com/logstash-plugins/logstash-filter-jdbc_static/issues/44 or https://github.com/logstash-plugins/logstash-integration-jdbc/issues/41 and I think it would make sense to hint on the documentation page that Apache Derby has some limitations.
For example the following paragraph:
This filter works by fetching data from a remote database, caching it in a local, in-memory Apache Derby database, and using lookups to enrich events with data cached in the local database. You can set up the filter to load the remote data once (for static data), or you can schedule remote loading to run periodically (for data that needs to be refreshed).
could be extended by:Please note that Apache Derby might not support the entire SQL syntax and feature-set of your backend/source/remote database. Features like
LIMITor bitwise operators (
<<and
>>) are not available when using this filter plugin.