Issues fixed in MarkLogic Server 11.0.3

sjs referencing XQuery modules with the same name may use the wrong module

When multiple XQuery modules with the same filename, but different paths exist in the modules database, SJS modules that reference the XQuery modules using the require function may not retrieve the correct module relative to the calling module.

Returning constraints from search endpoint results in invalid JSON

When using the "return-constraints" query option with JSON format, the JSON returned is in an invalid as there are multiple "constraint" properties at the same level.

SQL or Optic queries against sys_columns with query-based views is slow

If a Query-based view is present in the database, queries against the sys_columns data dictionary table from SQL or the Optic API will perform poorly.

The "property" querystring parameter is not supported in the v2/forests REST API

The documentation https://docs.marklogic.com/REST/GET/manage/v2/forests/[id-or-name]@view=counts states that "property" is a querystring parameter that can be used to request specific properties but it does not work.

Segmentation fault in xdmp::LogRecordCache::getAt () for xdmp:logfile-scan()

There can be a segmentation fault in xdmp::LogRecordCache::getAt () when using xdmp:logfile-scan() under certain conditions.

MarkLogic connections to AWS KMS and Azure KeyVault fail due to the use of TLSv1.0

AWS and Azure have discontinued the use of TLS 1.0 and 1.1 and now require TLS 1.2. MarkLogic does not yet support TLS 1.2 for communication with an external KMS so once AWS and Azure require TLS 1.2, MarkLogic will no longer be able to communicate with AWS KMS or Azure Key Vault.

format=json not supported for the counts and schema views in the manage REST API

When using the "counts" or "schema" views in the management REST API, the JSON format is not supported.

EBS volumes are not mounted with 'nodev flag

AWS EBS volumes are not mounted with 'nodev'. The scanner software is reporting that the mounted volumes should have the nodev flag applied

Segfaults while performing a rolling upgrade

When performing a rolling upgrade to 11.0.0 on multiple clusters that have been coupled for database replication, segfaults may be seen due to an incompatibility at the XDQP protocol level.

Protected Paths Fail When Protecting Elements at the Same Place with Different Attribute Value

With multiple protected paths protecting the same elements but different attribute value, some protected elements fail to be protected so they are visible to users who do not have the permission, while some other protected elements fail to show up to users who do have the permission. For example, given the two protected path '/foo/bar[@attribute="a1"]' and '/foo/bar[@attribute="a2"]'. Users with only the read permission for the first path might be able to see an element that's '/foo/bar[@attribute="a2"]', while users with only read permission for the second path might fail to see the element '/foo/bar[@attribute="a2"]'.

xdmp.filesystemFile returns xs.string Object instead of a JavaScript String

The xdmp.filesystemFile() function returns as an xs.string Object instead of a JavaScript String as documented.

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

Optic queries using either op.fromSearch()/op:from-search() or op.fromSearchDocs()/op:from-search-docs() operators may return more documents than theoretically accessible.

Curl Time Out When Backup to S3

MarkLogic might encounter the error `curlCode: 28, Timeout was reached` when doing backup to s3 in a very large cluster.

Geospatial triples of type LINESTRING or POLYGON are not deduplicated in SPARQL results

SPARQL queries that return newly inserted geospatial triples of type LINESTRING or POLYGON do not deduplicate results even with "dedup=on" option supplied.

Server hangs when turning log encryption on when telemetry is enabled

MarkLogic will hang when switching log encryption on if telemetry is enabled with log level set to info and the keystore component logs a warning or error message while enabling log encryption.

Slow region-relate queries in Geo in Optic while processing updates

While performing inserts to geospatial TDE columns or geospatial triples, slowdowns may occur if queries are performing region relate operations against these columns or triples. Region relate operations include 'CONTAINS', 'WITHIN', 'CROSSES', 'OVERLAPS', 'EQUALS', 'DISJOINT', 'INTERSECTS', 'TOUCHES', 'COVERS', and 'COVERED BY'