Skip to main content

Imply deprecations and removals

This page describes products and features that are deprecated or at end-of-life for Imply Polaris, Imply Enterprise, and Imply Hybrid. The information on this page is subject to change without prior notice.

When referring to deprecated or end-of-life statuses, Imply uses the following definitions:

Deprecated: The product or feature will be removed in a future release. No fixes or improvements to the product or feature are planned, but the product or feature will continue to work until removed. Imply strongly recommends that you migrate off the product or feature as soon as reasonable.

End-of-life: Imply no longer supports or recommends using the product or feature. No fixes or improvements to the product or feature will be made, and the product or feature's removal is imminent. Migrate off the product or feature as soon as possible.

When a product or feature is deprecated or planned for end-of-life, Imply reserves the following rights:

  • Extending the depreciation period and postponing the end-of-life.
  • Removing a feature or product prior to the end-of-life date in certain instances, including, but not limited to events such as the discovery of a security or query result correctness issue.

When possible, Imply will provide information to support your migration off of a deprecated product or feature prior to its removal.

Unless otherwise indicated, the planned deprecation and end-of-life year provided indicates the following:

  • Polaris: A release in the first half of that year
  • Enterprise and Hybrid: The first STS and LTS release of that year

In situations where the Polaris, STS or LTS dates differ for a feature, the entry indicates which product line it impacts.

2024 End-of-life​

Firehoses (STS)
Deprecation: Imply 3.4
Removed: 2024.08 STS
Polaris guidance: No action needed.
Enterprise and Hybrid guidance: Firehoses has not been the recommended ingestion method for several years. It is unlikely that you are using them. If you are, migrate to SQL-based ingestion (recommended) or JSON-based batch ingestion.

2025 End-of-life​

CentOS support for Imply Enterprise
Deprecation: 2024.09 STS, 2024.01.15 LTS
Planned end-of-life: March 2025
Polaris guidance: No action required.
Enterprise and Hybrid guidance: If you are using CentOS, migrate to a supported operating system: RHEL 7.x and 8.x or Ubuntu 18.04 and 20.04.
Java 8
Deprecation: 2024.09 STS, 2024.01.15 LTS
Planned end-of-life: 2025.01 STS and LTS
Polaris guidance: No action required.
Enterprise guidance: If you are using the Java 8 Runtime Environment, migrate to a supported version of Java, such as Java 17.
MVDs as the default for string array ingestion
Deprecation: 2024.10 STS, 2024.01.15 LTS
Planned end-of-life: 2025.01 STS and LTS, early 2025 Polaris
Polaris guidance: Will be provided.
Enterprise guidance: Starting in 2024.10 STS and 2025.01 LTS, SQL-based ingestion with the MSQ task engine will default to array typed columns instead of multi-value dimensions (MVDs). You must adjust your queries to either use array typed columns or explicitly specify your arrays as MVDs in your ingestion query. For more information, refer to the product feature update that Imply shared.
Firehoses (LTS)
Deprecation: Imply 3.4
Planned end-of-life: 2025.01 LTS
Enterprise and Hybrid guidance: Firehoses has not been the recommended ingestion method for several years. It is unlikely that you are using them. If you are, migrate to SQL-based ingestion (recommended) or JSON-based batch ingestion.
Inconsistent filter null handling moving to three-valued logic (Polaris and STS)
Deprecation: 2023.12
Planned end-of-life: 2025.01 STS, early 2025 Polaris
Note: This removal date is planned for the Polaris and STS releases. Previously, Imply's distribution of Apache Druid®'s behavior for filters was inconsistent. Some filters used two-valued logic while others used three-valued logic.
Polaris guidance: This change does not impact most users. If you are impacted, adjust your queries and any downstream apps for consistent three-valued logic. The process is the same as described for Enterprise and Hybrid. For more information, see Migration guide: SQL compliant mode.

Enterprise and Hybrid guidance: The default for Imply's distribution of Apache Druid® has been to use three-valued logic consistently since 2023.11 STS and 2024.01 LTS.

The ability to use the inconsistent two-valued logic will be removed at the end-of-life date, and only three-valued logic will be supported.

Adjust your queries and any downstream apps for consistent three-valued logic. For more information about how three-valued logic differs from two-valued logic, see Migration guide: SQL compliant mode.

Non-SQL compliant null handling (Polaris and STS)
Deprecation: 2023.12
Planned end-of-life: 2025.01 STS, early 2025 Polaris
Note: This removal date is planned for the STS release. LTS will maintain non-SQL compliant null handling in a deprecated state for the 2025 release.
Polaris guidance: This change does not impact most users. If you are impacted, adjust your queries and any downstream apps for ANSI-compliant null handling. The process is the same as described for Enterprise and Hybrid. For more information, see Migration guide: SQL compliant mode.
Enterprise and Hybrid guidance: Adjust your queries and any downstream apps for ANSI-compliant null handling. For more information, see Migration guide: SQL compliant mode.
Non-strict Booleans (Polaris and STS)
Deprecation: 2023.12
Planned end-of-life: 2025.01 STS, early 2025 Polaris
Note: This removal date is planned for the STS release. LTS will maintain non-SQL compliant non-strict Boolean logic in a deprecated state for the 2025 release.
Polaris guidance: This change does not impact most users. If you are impacted, adjust your queries and any downstream apps for ANSI-compliant Boolean logic. The process is the same as described for Enterprise and Hybrid. For more information, see Migration guide: SQL compliant mode
Enterprise and Hybrid guidance: Adjust your queries and any downstream apps for ANSI-compliant Boolean logic. For more information, see Migration guide: SQL compliant mode.
JSON v3 and v4
Deprecation: 2023.09 STS, 2024.01 LTS
Planned end-of-life: 2025.01 STS and LTS
Polaris guidance: No action required.
Enterprise and Hybrid guidance: After upgrading to a version with support for a higher JSON version, you cannot downgrade to an earlier version. Imply's distribution of Apache Druid® has been on JSON v5 since the 2024.01 LTS and 2023.09 STS.
Segment loading rules
Deprecation: 2023.08 STS and 2023.01.8 LTS
Planned end-of-life: 2025.01 STS and LTS
Polaris guidance: No action required.
Enterprise and Hybrid guidance: No action needed. The replacement segment loading process, smart segment loading, automatically calculates the optimal values for settings you previously had to manually set. As a result, the following settings will be automatically ignored: maxSegmentsInNodeLoadingQueue, maxSegmentsToMove, replicantLifetime, balancerComputeThreads. Additionally, the cachingCost balancer strategy is no longer supported.
SysMonitor
Deprecation: 2023.08 STS and 2023.01.8 LTS
Planned end-of-life: 2025.01 STS and LTS, early 2025 Polaris
Polaris guidance: No action required.
Enterprise and Hybrid guidance: Use OSHI system monitor instead. For more information, see OshiSysMonitor module.
druid.azure.endpointSuffix
Deprecation: 2024.03 STS, 2024.01.6 LTS, March 2024 Polaris
Planned end-of-life: 2025.01 STS and LTS, early 2025 Polaris
Polaris guidance: No action required.
Enterprise and Hybrid guidance: Update any references to use druid.azure.storageAccountEndpointSuffix instead.
AsyncSQL download (old)
Deprecation: 2024.01 STS and LTS, January 2024 Polaris
Planned end-of-life: 2025.01 STS and LTS, early 2025 Polaris
Note: This entry refers to an older version of async SQL download that has been replaced with a new version with the same name. For more information, see Download data.
Polaris guidance: No action required.
Polaris guidance: Will be provided.
Enterprise and Hybrid guidance: Use the new version of Async SQL download. For more information, see Download data.
ioConfig.inputSource.type.azure storage schema
Planned deprecation: 2025.01 STS and LTS, early 2025 Polaris
Planned end-of-life: 2026.01 STS and LTS, early 2026 Polaris
Polaris guidance: No action required.
Enterprise and Hybrid guidance: Update your ingestion specs to use the azureStorage storage schema, which provides more capabilities.

2026 End-of-life​

Inconsistent filter null handling moving to three-valued logic (LTS)
Deprecation: 2023.12
Planned end-of-life: 2026.01 LTS
Note: This entry is for the LTS. For other releases, see the corresponding STS and Polaris entry. Previously, Imply's distribution of Apache Druid® behavior for filters was inconsistent. Some filters used two-valued logic while others used three-valued logic. The usage of two-valued logic is being removed. Three-valued logic will be used consistently.
Polaris guidance: No action required.

Enterprise and Hybrid guidance: The default for Imply's distribution of Apache Druid®'s has been to use three-valued logic consistently since 2023.11 STS and 2024.01 LTS.

The ability to use the inconsistent two-valued logic will be removed at the end-of-life date, and only three-valued logic will be supported.

Adjust your queries and any downstream apps for consistent three-valued logic. For more information about how three-valued logic differs from two-valued logic, see Migration guide: SQL compliant mode.

Non-SQL compliant null handling (LTS)
Deprecation: 2024.01 LTS
Planned end-of-life: 2026.01 LTS
Note: This entry is for the LTS. For other releases, see the corresponding STS and Polaris entry.
Polaris guidance: No action needed.
Enterprise and Hybrid guidance: Adjust your queries and any downstream apps for ANSI-compliant null handling. For more information, see Migration guide: SQL compliant mode.
Non-strict Booleans (LTS)
Deprecation: 2024.01 LTS
Planned end-of-life: 2026.01 LTS
Note: This entry is for the LTS. See the corresponding STS and Polaris entry.
Polaris guidance: No action required.
Enterprise and Hybrid guidance: Adjust your queries and any downstream apps for ANSI-compliant Boolean logic. For more information, see Migration guide: SQL compliant mode.
ZooKeeper-based task discovery
Planned deprecation: 2025.01 STS and LTS
Planned end-of-life: 2026.01 STS and LTS
Polaris guidance: No action required.
Enterprise and Hybrid guidance: Use HTTP-based task discovery instead, which has been the default since 2022.

2027 End-of-life​

Row-based subquery limits
Planned deprecation: 2026.01 STS and LTS
Planned end-of-life: 2027.01 STS and LTS
Polaris guidance: No action required.
Enterprise and Hybrid guidance: The default for this guardrail will change from row-based to byte-based in 2025.01 STS and LTS. If you use subquery limits, change any row-based subquery limits to be byte-based instead. For more information, see Guardrails for materialization of subqueries.