- [DOC] Updated docs to correct name of parse_options config option #75
- Fix: exceptions thrown while handling events no longer crash the pipeline #73
- Feat: added parser_options for more control over XML parsing #68
- Fixed creation of empty arrays when xpath failed #59
- Fixed force_array behavior with nested elements #57
- Update gemspec summary
- Fix some documentation issues
- Fix a bug that, when the plugin tried to report an invalid configuration, would report the following instead of the real error: translation missing: en.logstash.agent.configuration.invalid_plugin_register
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- breaking,config: New configuration
suppress_empty. Default to true change default behaviour of the plugin in favor of avoiding mapping conflicts when reaching elasticsearch - config: New configuration
force_content. By default the filter expands attributes differently from content in xml elements. This option allows you to force text content and attributes to always parse to a hash value. - config: Ensure that
targetis set when storing xml content in the event (store_xml => true)
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- Added setting to disable forcing single values to be added in arrays. Ref: #28.
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Refactored field references, code cleanups
- Support for namespace declarations to use parsing the XML document
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0