Logi Composer Version 5 Release Notes
These release notes cover changes and fixes made to Zoomdata and Composer 5 releases. You can identify your release version on the login screen.
Support for Composer 5.9 ends on June 27, 2022. Composer 6.9 will soon enter the Passive Support phase. Our Passive Support release receives only critical patches and security updates until its end-of-life date. We describe critical patches in the Passive Support Release Notes page at the discretion of Product Management. Security updates are not applicable to the third-party dependencies. If you are using Composer 5.9, you should contact Sales and upgrade to the most current LTS release. We no longer publish documentation for any Composer products prior to version 6.9. Contact Customer Support if you need content for an unsupported release.
Support for Zoomdata 4.9 will end on September 25, 2021. With the release of Composer 6.9 LTS, Zoomdata 4.9 entered Passive Support. Our LTS Passive Support release receives only critical patches and security updates until its end-of-life date. Security updates are not applicable to the third-party dependencies. We encourage you to migrate to our most current LTS release. The documentation for the LTS Passive Support release is updated only when necessary. If there are changes to existing functionality or workarounds that you need to be aware of, you can find the information you need in the Release Notes.
For information about the supported Composer and Logi Zoomdata releases, see Logi Composer (Zoomdata) Release Vehicles.
Important CentOS 6 Information
CentOS 6 is no longer supported and the special installation Bootstrap procedure (
bootstrap-zoomdata-centos6.run) is no longer provided with this product. CentOS 6 is no longer supported by Red Hat Linux (RHEL). Use CentOS 7 or 8 instead.
Important Ubuntu Information
Ubuntu users who have Composer or Zoomdata versions earlier than 5.8 installed must first remove the legacy repository before upgrading Composer 5.8 or later. Use this command:
sudo rm -f /etc/apt/sources.list.d/saltstack.list
Email email@example.com to purchase Composer.
For information about Composer's end-of-life policy for third-party software, see Composer's Third-Party End-of-Life Policy.
Upgrade and Migration Considerations
Before installing or upgrading to any Composer 5.9.x version, please read Composer 5.9.x Installation and Upgrade Process for Multiple Context Paths.
If you are upgrading to a newer version of Composer and you also want to change your encryption mode, perform the upgrade first and complete the steps described in Changing the Encryption Mode.
Manually upgrading Composer no longer provides the Java Runtime Environment (JRE) needed for Composer to start. Make sure you have Java 11.0.5 or later installed before you manually install or manually upgrade to Composer 5.8 or later. If you do not, Composer will not start.
Due to the upgrade of the HashiCorp Consul (service discovery) version from 0.7.5 to 1.2.2, custom connectors built before Zoomdata 3.2 ( built for versions 3.1 or earlier versions) will not appear after you migrate to Zoomdata 3.7 (or later) or to Composer 5 (or later). This is caused by incompatibilities between old connectors and the new Consul. To make your custom connectors compatible with Zoomdata 3.7 (or later) and Composer 5 (or later), you must migrate the connectors as described in Custom Connector Migration.
This migration step is required only for custom connectors built with Zoomdata versions earlier than 3.2 or for connectors that were present before Zoomdata 3.2 but that are now deprecated (for example, the Hive on Tez connector, which was replaced by the Hive connector in Zoomdata 3.7).
Zoomdata version 3.2 (or later) and Composer 5 (or later) versions use headless Google Chrome instead of Firefox for the Screenshot microservice. See Setting Up the Screenshot Microservice.
Log4j and Log4net Vulnerabilities Update
In the second week of December 2021, a Log4j vulnerability was announced that may affect some customers using our products. Resolving/mitigating this issue is a high priority! We will continue to issue information to help you with this vulnerability. For more information see Statement on Log4j and Log4net Vulnerabilities.