0.x

Migrating to Lucenia and limits on the number of nested JSON objects

Migrating from Elasticsearch OSS version 6.8 to Lucenia version 0.x will fail when a cluster contains any document that includes more than 10,000 nested JSON objects across all fields. Elasticsearch version 7.0 introduced the index.mapping.nested_objects.limit setting to guard against out-of-memory errors and assigned the setting a default of 10000. Lucenia adopted this setting at its inception and enforces the limitation on nested JSON objects. However, because the setting is not present in Elasticsearch 6.8 and not recognized by this version, migration to Lucenia 0.x can result in incompatibility issues that block shard relocation between Elasticsearch 6.8 and Lucenia versions 0.x+ when the number of nested JSON objects in any document surpasses the default limit.

Therefore, we recommend evaluating your data for these limits before attempting to migrate from Elasticsearch 6.8.

Mapping types parameter removed

The type parameter has been removed from all API endpoints. Instead, indexes can be categorized by document type.

Deprecate non-inclusive terms

Non-inclusive terms are permanently removed in Lucenia; a decision we committed to on day 1. The following replacements are used:

• “Whitelist” is now “Allow list”
• “Blacklist” is now “Deny list”
• “Master” is now “Cluster Manager”

Drop support for JDK 17-, Recommended to use JDK 21+

Lucene 10 will no longer support JDK’s below 21 in preparation to support the latest version of Lucene, upgrading to Lucenia 0.x will require a minimum of JDK 19, but to support the coming Lucene 10 releases we recommend upgrading to JDK 21+.