Bug Fix Report
Generate a Fixed Bugs Report for a single version, or for all bugs fixed between any two versions (inclusive).
| Found 17 bugs fixed in 9.0-9.1 |
| Bug ID | Component | Platform | Status |
| ODBC Performance & Debugging | |||
| Data accessed via ODBC is slow. Unable to disable ODBC debugging. | |||
| BUG-51855 | SQL | windows(64-bit) | Fixed in 9.0-9.1 |
| SQL result double values truncated over ODBC | |||
| SQL result double values are incorrectly truncated to six digits of precision over ODBC. | |||
| BUG-51913 | SQL | all | Fixed in 9.0-9.1 |
| Segmentation fault | |||
| Segmentation fault in xdmp::ScratchExpandedTreeStorage::addBinaryNode | |||
| BUG-51892 | xdmp | all | Fixed in 9.0-9.1 |
| PowerBI & boolean types | |||
| Booleans do not work in PowerBI | |||
| BUG-51914 | SQL | all | Fixed in 9.0-9.1 |
| ECDH key exchange | |||
| ECDH key exchange support now available with this release | |||
| BUG-51978 | security | all | Fixed in 9.0-9.1 |
| Optimizations on timestamp functions in SQL | |||
| Power BI data slicer on date column produces inefficient queries that has filters not a candidate for index scan. Rewriting the query in an optimized way will fix the query to still use index scan. | |||
| BUG-51779 | SQL | all | Fixed in 9.0-9.1 |
| A nested for with an order by may segfault | |||
| Under some circumstances, a 'for' within a 'for' with an order by clause with multiple ordering constraints may cause a segmentation fault. The pattern is 'for... for... order by $something, $another ... return ...' | |||
| BUG-51848 | xdmp | all | Fixed in 9.0-9.1 |
| Temporal updates combined with node updates may create duplicate documents | |||
| Performing a temporal update and a non-temporal node update in the same statement may create duplicate documents. | |||
| BUG-52010 | Bi-Temporal | all | Fixed in 9.0-9.1 |
| HTTP Server mishandles HTTP requests with zero headers | |||
| The server does not return appropriate response to HTTP requests with zero headers | |||
| BUG-51958 | xdmp | all | Fixed in 9.0-9.1 |
| Integer scalar type treated as strings in PowerBI | |||
| Have PowerBI treat xs:integer as a string. This is because xs:integer can have values outside of the range of PowerBI's biggest data type, the Whole Number. See https://docs.microsoft.com/en-us/power-bi/desktop-data-types Because of this limitation, PowerBI cannot "fold" direct query expressions with xs:integer. Recommend using xs:int instead of xs:integer in PowerBI. If you need bigger numbers than xs:int can hold, recommend using xs:long. Updated xs:integer to be casted as char in the Direct Query connector unless this PowerBI limitation is addressed by Microsoft. | |||
| BUG-51916 | SQL | all | Fixed in 9.0-9.1 |
| Complex fields with range indexes and tokenizer overrides Segfault | |||
| Given a field defined with a range index and tokenizer overrides, inserting, reindexing, refragmenting, replicating, or rebalancing a document has an instance of the field that involves multiple child elements may cause a segmentation fault in the tokenizer. | |||
| BUG-51894 | Stemming and Tokenization | linux(64-bit) | Fixed in 9.0-9.1 |
| Redaction fails for JSON objects with colon in key name | |||
| When there are JSON object with colon in key name like "foo:bar", redactions in child nodes below this level are not redacted | |||
| BUG-51650 | Redaction | all | Fixed in 9.0-9.1 |
| Long casted as float in PowerBI issued queries | |||
| Long type data shouldn't be casted as a float when using the MarkLogic direct query data connector. | |||
| BUG-51917 | SQL | all | Fixed in 9.0-9.1 |
| SQL query optimization for "is NULL" and "is not NULL" on a non-nullable column | |||
| SQL queries containing conditions “column is NULL” and “column is not NULL” on a non-nullable column will be optimized. Also when these kind of filters are used in “OR”/”AND” condition with other filters in SQL queries, then relevant optimizations will be applied to simplify the filter processing. | |||
| BUG-51898 | SQL | all | Fixed in 9.0-9.1 |
| mlcmd won't create duplicate /etc/fstab records when the VM reboots on Azure | |||
| When deploy MarkLogic on Azure VMs, mlcmd will try to format and mount disk every time it runs. Although the formatting and mounting operation will fail but a record will be appended to /etc/fstab. | |||
| BUG-51945 | Utility Computing | Azure | Fixed in 9.0-9.1 |
| Support for client certificates that don't identify themselves | |||
| When creating a client certificate, you can now add a "certificate-type=client" parameter to the secure-credentials request to explicitly identify the certificate as a client certificate if it does not include the extension attribute that says it is. | |||
| BUG-51934 | Common API | all | Fixed in 9.0-9.1 |
| PowerBI String/text Data Slicer optimization | |||
| The String/text Data Slicer (in Power BI) currently produces SQL that is not optimal. | |||
| BUG-51870 | SQL | all | Fixed in 9.0-9.1 |