Issues fixed in MarkLogic Server 10.0-2.1
- Last Updated: April 6, 2026
- 1 minute read
- MarkLogic Server
- Documentation
Released: Oct 1, 2019
The following issues have been addressed in this release:
| Platform | Component | Bug ID | Details |
|---|---|---|---|
| all | XSLT | BUG-53134 | XSLT-DEFAULTCOLL erroneously raised If an XSLT stylesheet includes a default-collations attribute with multiple collations, and any one of them is unrecognized, XSLT-DEFAULTCOLL will be raised, even if some other collation in the list is recognized. |
| all | Encryption at REST | BUG-53230 | Support ARN's for AWS KMS Please note that starting with 9.0-10.3 and 10.0-2.1, users will be able to use encryption keys having the ARN syntax when specifying AWS-KMS key IDs. This allows you to specify keys from other AWS accounts. Previously, this was not supported. |
| all | XSLT | BUG-53235 | XSLT reports bogus XSLT-APPTEMPCTXNOTNODE Under some circumstances involving a template with a complex body that includes evaluation of an XPath that end with a value step (not a node step), XSLT may incorrectly raise the error XSLT-ATTTEMPCTXNOTNODE. This may manifest in Schematron processing also. |
| all | Entity Services | BUG-53169 | Calling gradle mlUpdateIndexes on artifact produced from gradle hubSaveIndexes fails The gradle call mlUpdateIndexes fails on an artifact produced from gradle hubSaveIndexes with an error saying that the lexical value "zxx" is not valid for dbprop:language. |