Issues fixed in MarkLogic Server 9.0-3.1
- Last Updated: April 6, 2026
- 1 minute read
- MarkLogic Server
- Documentation
Released: Oct 27, 2017
The following issues have been addressed in this release:
| Platform | Component | Bug ID | Details |
|---|---|---|---|
| windows(64-bit) | Encryption at REST | BUG-47691 | Upgrade to 9.0-3 with encrypted configuration files fails Upgrade to 9.0-3 with encrypted configuration files fails, resulting in an unrecoverable configuration. |
| all | Geospatial | BUG-47804 | Geospatial region index fails during rolling upgrade to 9.0-3 A cts:geospatial-region-query executed on a 9.0-3 E-node in a mixed cluster with 9.0-2 D-nodes will fail with a XDMP-CANTDECODEQUERYKIND error. Inserting data into the geospatial region index in this mixed cluster scenario can result in corrupted data. |
| all | SQL | BUG-47702 | Error in running SQL/SPARQL during rolling upgrade from 9.0-1/9.0-2 to 9.0-3 During Rolling upgrade from 9.0-1 to 9.0-3, or from 9.0-2 to 9.0-3, SQL/SPARQL query can run into error. Avoid upgrade 9.0-1/9.0-2 to 9.0-3. Instead, Upgrade from 9.0-1 to 9.0-3.1 Upgrade from 9.0-2 to 9.0-3.1 |
| linux(64-bit) | Upgrade | BUG-47924 | Merge after upgrade to 9.0-3 corrupts on-disk geospatial region indexes This bug occurs when data is loaded into a geospatial region index in a previous version, and the host is upgraded to 9.0-3. If the on-disk stand containing the index is merged, the resulting index may be corrupted. Queries and subsequent merges may fail with XDMP-CORRUPT errors, or queries may return incorrect results. |
| all | Geospatial | BUG-47720 | Memory leak in geospatial region queries On MarkLogic Server version 9.0-3, there is a memory leak resulting from calls to cts:geospatial-region-query when using the "intersects" operation. |
| all | Telemetry | BUG-47701 | Default telemetry endpoint is incorrect. Default telemetry endpoint is incorrect. |