Skip to main content

What's New in MarkLogic 11

Release Notes

MarkLogic 11.1.0

MarkLogic 11.1.0 is a minor release that adds a number of new features and addresses a number of bugs and security vulnerabilities highlighted here:

  • Automatic cache sizing will now allocate caches using the recommended ratios for hosts with up to 512 GB of RAM. Additional testing and tuning will be required to increase automatic calculation for hosts with more that 512 GB of RAM in later releases. 

  • Starting in MarkLogic 11.0.0, the Optic/SPARQL query plan viewer in Query Console shows the memory component of each step in the plan as "NaN". This is fixed in 11.1.0.

  • Fixed an issue where xdmp:logfile-scan() might only return part of the lines for log entries that have many lines.

  • Fixed an issue in the Admin Interface that causes replica databases when database encryption is enabled to report that the encrypted size is zero.

  • Fixed an issue in the Admin Interface that prevented the modules database from being set for the triggers in a database.

  • Fixed an issue in Query Console where Select all via [ctrl]+[A] was working incorrectly when selecting in the query buffer or results panel.

  • Fixed an issue in Query Console that prevented copying and pasting the documentation from the autocomplete pop-up.

  • Added support for backups to S3 buckets with object lock and compliance retention activated.

  • Added support for a new  "extension" option to xdmp:document-filter() and xdmp.documentFilter() that fixes an issue where the file type may not be detected correctly because the function does not know the file extension which otherwise comes from the document URI.

  • Fixed multiple issues with the segment assignment policy:

    • Fixed the issue that causes potential data loss when using segment policy and retired forests.

    • Fixed the issue that causes potential data loss when rebalancing with the segment policy.

    • Fixed the issue that causes an increase of deadlocks during rebalancing.

  • Improved error messages for XDMP-LEXVAL errors.

  • Improved error handling when too many values are passed into calls to cts:triple-range-query().

  • Fixed performance regression starting from 10.0-9 where an optimization for certain cts:triples() patterns that were added caused other triple range queries with cts:triples() queries to be slower.

  • The metrics for "external" join and sort are now available via the REST API /manage/v2/meters GET endpoint.

  • Added missing support for the cts.documentFormatQuery(), cts.documentRootQuery(), and cts.documentPermissionQuery() query constructors to Optic DSL.

  • Upgraded the libraries in XCC and mlcp to address multiple security vulnerabilities

    Notice

    Due to the Java version requirements of the updgraded 3rd party libraries, mlcp now requires JRE 11 or later. 

  • There is a known issue with mlcp loading compressed RDF files from zip archives where the individual RDF file is over 2 GB. This will be fixed in the next release.

To review the full list of bug fixes included MarkLogic 11.1.0, visit the BugTrack page on the MarkLogic Support Portal. Select the "From" version you would like to start with and set the "To" version to "11.1.0".

MarkLogic 11.0.3

MarkLogic 11.0.3 is a patch release that addresses a number of bugs and contains some performance improvements. The following are some of the highlights:

  • op.fromSearch() and op.fromSearchDocs() security constraints 

    • Starting with MarkLogic 10.0-6, Optic queries using either op.fromSearch()/op:from-search() or op.fromSearchDocs()/op:from-search-docs() operators may return more documents than theoretically accessible. This has been fixed in 11.0.3 as well as 10.0-6.6, 10.0-7.4, 10.0-8.5, 10.0-9.7, and 10.0-10.2.

  • The v1/search REST API with the "return-constraints" query option and JSON format now returns valid JSON even if there are multiple constraints

  • Fixed an issue where segfaults can happen when performing rolling upgrades to 11.0.0 on multiple clusters that have been coupled for database replication

  • Element Level Security fix

    • If multiple protected paths are protecting the same elements with different attribute values, some protected elements fail to be protected while some other protected elements fail to show up to users who should have access

  • Geospatial triples of type LINESTRING or POLYGON are now deduplicated correctly in SPARQL results

  • Performance improvement of region relate queries such as 'CONTAINS', 'WITHIN', 'CROSSES', 'OVERLAPS', 'EQUALS', 'DISJOINT', 'INTERSECTS', 'TOUCHES', 'COVERS', and 'COVERED BY' that are run while updates are occurring

  • Fixed an issue where users might encounter the error `curlCode: 28, Timeout was reached` when doing backups to s3 in very large clusters

  • Improved performance of SQL or Optic queries against sys_columns with query-based views

  • In a AWS Managed Cluster, EBS volumes are now mounted with 'nodev' flag and the /var/tmp/marklogic.host file is written with permissions of rw-rw-rw-

  • Fixed an issue where the server hangs when turning log encryption on when telemetry is enabled

  • Connections to AWS KMS, Azure KeyVault and other key management systems now support TLSv1.2

  • Fixed an issue where server-side JavaScript code referencing XQuery modules with the same name may have used the wrong module

  • The "property" query string parameter is now supported in the v2/forests REST API

  • Fixed multiple security vulnerabilities in XCC and mlcp:

    • CVE-2007-1157

    • CVE-2022-45688 

To review the full list of bug fixes included MarkLogic 11.0.3, visit the BugTrack page on the MarkLogic Support Portal. Select the "From" version you would like to start with and set the "To" version to "11.0.3".

MarkLogic 11.0.2

MarkLogic 11.0.2 is a patch release that addresses a number of bugs in MarkLogic 11.0.0. The following are some of the highlights:

  • Admin UI improvements

    • Performance improvements to the status pages for large clusters or databases with hundreds of forests

    • Improved form input validation for certificate templates

    • Report when there are hosts in the cluster on different patch versions

  • Performance improvements for Optic fromSearchDocs() and joinDocCols() 

  • Performance improvements for starting backups of databases with a large number of forests

  • The new health check REST endpoint is now configured correctly when upgrading from an earlier version

  • Performance and stability improvements for backups to S3

  • Addressed an error in PDF conversion

  • Fixed op.xpath() support for XPaths that start with ./ or ../

  • Addressed a SQL issue where LEFT JOIN with IS NULL condition on a nullable column unexpectedly returned no results

  • Addressed a SPARQL issue where certain queries with OPTIONAL clauses returned the wrong results

  • Added support for new AWS EC2 instance types

  • Addressed an issue with scheduling of weekly backups

  • Addressed an issue with serialization of CTS queries for Query-Based Views

To review the full list of bug fixes included MarkLogic 11.0.2, visit the BugTrack page on the MarkLogic Support Portal. Select the "From" version you would like to start with and set the "To" version to "11.0.2".

MarkLogic 11.0.0

MarkLogic 11.0.0 includes fixes for a number of existing bugs. The following are some of the highlights:

  • mlcp now handles splits with multi-byte content

  • AWS Managed Cluster capability now better handle EBS volume and ENI reattachment for failed instances

  • Reindexing is now triggered automatically when creating range indexes that use document properties

  • Search results are now correct for JSON documents with "lang" or "language" property

  • Libraries have been upgraded to address security vulnerabilities

To review the full list of bug fixes included MarkLogic 11.0.0, visit the BugTrack page on the MarkLogic Support Portal. Select the "From" version you would like to start with and set the "To" version to "11.0.0".

In this section: