Date: Fri, 04 Sep 2020 13:53:06 +0000 From: bugzilla-noreply@freebsd.org To: elastic@FreeBSD.org Subject: [Bug 249108] sysutils/logstash7: Update to 6.9.1 Message-ID: <bug-249108-37421@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249108 Bug ID: 249108 Summary: sysutils/logstash7: Update to 6.9.1 Product: Ports & Packages Version: Latest Hardware: Any URL: https://www.elastic.co/guide/en/logstash/current/logst ash-7-9-1.html OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: elastic@FreeBSD.org Reporter: juraj@lutter.sk Flags: maintainer-feedback?(elastic@FreeBSD.org) Assignee: elastic@FreeBSD.org Attachment #217745 maintainer-approval+ Flags: Flags: maintainer-feedback+ Created attachment 217745 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D217745&action= =3Dedit sysutils/logstash7: Update to 7.9.1 Hi, please find the patch attached. Changelog: * Notable issues fixed: - Fixes in Docker image configuration of Monitoring and Central Managemen= t: - As more and more users adopt our docker images, we=E2=80=99ve been ge= tting reports on gaps where these images don=E2=80=99t provide all the configurat= ion knobs the other artifacts do. This release exposes more environment variables for configuring proxy support and certificate verification mode for monitoring = and central management , and for configuring verification_mode - Pipeline execution fixes to flushing and shutdown - Since 7.2.0, a change caused terminating pipelines to not request inp= ut plugins to cleanup before shutdown, which could cause leaks in resources th= at weren=E2=80=99t freed during pipeline reloads. You can find more informatio= n on the fix here: - Logstash supports ordered execution for pipelines with a single worke= r. A bug was found in this mode where the flushing mechanism wasn=E2=80=99t work= ing, preventing plugins like the aggregate filter from working correctly. This h= as been fixed, and you can read the details here: * Consistent Fingerprinting: - Our fingerprint filter is a popular solution to perform deduplication of data in downstream systems like Elasticsearch, by computing a hash value ba= sed on data from each event. Users reported that this filter could produced different values for events containing the same data since it didn=E2=80=99= t ensure the order in which Hash Maps/Objects/Ruby Hashes processed their key/value pair= s. This has now been fixed, and you can read more about how it was solved and = all the tests we=E2=80=99ve done here: * Updated JRuby to 9.2.13.0: - The new JRuby release brings greater stability to its code optimization= s in multithreaded workloads and a fix to exception handling in Windows environments, both issues that could affect our users. See the JRuby release notes for more information. * Plugins: - Avro Codec - 3.2.4 - [DOC] Add clarifications on partial deserialization - Fingerprint Filter - 3.2.2 - Fixed lack of consistent fingerprints on Hash/Map objects - Kv Filter - 4.4.1 - Fixed issue where a field_split_pattern containing a literal backslash failed to match correctly - Elasticsearch Input - 4.7.1 - [DOC] Updated sliced scroll link to resolve to correct location after= doc structure change - [DOC] Added usage example of docinfo metadata - Http_poller Input - 5.0.2 - [DOC]Expanded url option to include Manticore keys - Snmp Input - 1.2.5 - Updated snmp4j library to v2.8.4 - Fixed: support SNMPv3 multiple identical security name with different credentials - Fixed: multithreading problem when using multiple snmp inputs with multiple v3 credentials - Syslog Input - 3.4.4 - Refactor: avoid global side-effect + cleanup - avoid setting BasicSocket.do_not_reverse_lookup as it has side effects for others - Jdbc Integration - 5.0.6 - DOC:Replaced plugin_header file with plugin_header-integration file. - Rabbitmq Integration - 7.1.1 - DOC:Replaced plugin_header file with plugin_header-integration file. - Elasticsearch Output - 10.6.2 - [DOC] Added clarifying info on http compression settings and behaviors - [DOC] Fixed entry for ilm_policy default value Testport results: https://freebsd-stable.builder.wilbury.net/data/11_4_RELEASE_GENERIC-defaul= t/2020-09-03_21h31m39s/logs/logstash7-7.9.1.log https://freebsd-stable.builder.wilbury.net/data/12_STABLE_GENERIC_amd64-def= ault/2020-09-03_23h40m09s/logs/logstash7-7.9.1.log https://freebsd-current.builder.wilbury.net/data/13_CURRENT_GENERIC_amd64-d= efault/2020-09-04_14h49m05s/logs/logstash7-7.9.1.log Approving on behalf of elastic@ --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-249108-37421>