{"id":2685,"date":"2017-02-16T06:00:47","date_gmt":"2017-02-16T14:00:47","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/?p=2685"},"modified":"2025-06-13T20:28:14","modified_gmt":"2025-06-14T03:28:14","slug":"announcing-couchbase-server-4-6-whats-new-improved","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/announcing-couchbase-server-4-6-whats-new-improved\/","title":{"rendered":"Announcing Couchbase Server 4.6 – What’s New and Improved"},"content":{"rendered":"

Couchbase delivers the Couchbase Data Platform that powers Web, Mobile, and IoT applications for digital businesses. With our newest release, Couchbase Server 4.6 provides the availability, scalability, performance, and security that enterprises require for their mission-critical applications.<\/p>\n

What’s New and Improved<\/h3>\n

Query<\/h4>\n

The new string, date, array, and JSON object functions that have been added to N1QL simplify data transformations and provide richer query expressions.Faster queries in N1QL are the result of several query engine performance enhancements across many types of operations, including joins and index scans.<\/p>\n

Check out documentation for String functions,\u00a0<\/a> Date functions,<\/a> Array functions<\/a> and Object functions<\/a>.<\/p>\n

Replication<\/h4>\n
\n

Cross datacenter replication (XDCR) with timestamp-based conflict resolution makes it easier for applications to implement a Last Write Wins (LWW) document conflict management policy across multiple Couchbase clusters. The per-document timestamp combines the server logical and physical clocks together, forming a hybrid logical clock and timestamp, which enables easy identification of consistent document snapshots across distributed Couchbase clusters.<\/p>\n

Check out documentation for Timestamp-based conflict resolution<\/a>.<\/p>\n

Security<\/h4>\n

Adding support for Pluggable Authentication Modules (PAM) simplifies centralized password and policy management across servers. It also enables use of existing password management services for a Couchbase cluster (for example, Linux \/etc\/shadow).The new server secret management feature provides improved enterprise security compliance and a more security-hardened Couchbase Server.<\/p>\n

Check out documentation for Pluggable Authentication Modules<\/a> and Secret management<\/a>.<\/p>\n<\/div>\n

Tools [Developer Preview]<\/h4>\n
\n

It is now easier than ever to move data in and out of Couchbase Server using the new flexible import and export tools. cbimport imports data from a CSV file or a JSON document. cbexport exports data as a JSON document.<\/p>\n<\/div>\n

<\/div>\n
Check out documentation for Cbimport<\/a> and Cbexport<\/a>.<\/div>\n
<\/div>\n

<\/h4>\n

Data Access<\/h4>\n
\n
\n
Adding direct support for lists, maps, sets, and queues in the sub-document API using the new data structure SDK feature, further simplifies application development. The new data structures work seamlessly with the same underlying data representation, allowing developers in N1QL, Java, .NET, and other languages to access the same data across different programming languages and interfaces.Adding .NET Core support enables Microsoft application developers to easily develop and integrate their applications with<\/div>\n
Couchbase Server.<\/div>\n
<\/div>\n
<\/div>\n
Check out documentation for Data structures<\/a> and .NET Core blog<\/a>.<\/div>\n
<\/div>\n<\/div>\n<\/div>\n

<\/h4>\n

Search [Developer Preview 2]<\/h4>\n

Search adds support for MossStore, the new default kv store mechanism for full text indexes in FTS. MossStore is part of Moss<\/a> (\u201cMemory-oriented sorted segments\u201d), a simple, fast, persistable, ordered key value collection implemented as a pure Golang library.You can now create custom index mappings using the document key to determine the type and with this enhancement, so it\u2019s easier to support the common data modeling style in which the document type is indicated by a portion of the key. This release also lets you sort search results by any field in the document, as long as that field is also indexed. In the earlier releases, search results were always returned in order of descending relevance score.<\/p>\n

Check out documentation for Index Type Mapping By Keys<\/a> and Sorting Query Results<\/a>.<\/p>\n

Here are some resources to get you started –<\/p>\n