4.3-beta-1 (June 19 2017)¶

ENGINE-1073 Allow indexValues, values, and export APIs to export the indexed groupBy value¶

The indexValues, values, and export APIs now all support expose the indexed groupBy value for an item. Previously you would get no value back if requested.

ENGINE-1072 Streaming export API¶

The new streaming export API that can be used to export all data or to retrieve all results from a query. The results are not sorted and are returned in an unstable order. Subsequent calls are not guaranteed to return the results in the same order.

It supports regular search criteria and can output a combination of meta data (id, score, exact), item properties, and indexed values.

It does not support sortBy, groupBy or any pagination specific features from the query API.

See Export API for more details.

ENGINE-1071 Upgrades Apache Lucene from 6.5.1 to 6.6.0¶

The Apache Lucene library has been upgraded from 6.5.1 to 6.6.0.

ENGINE-1070 Upgrades dependent libraries¶

Upgrades dependent libraries.

ENGINE-1069 Index values should use LeafReader instead of MultiReader¶

The indexValues and values APIs now use LeafReader instead of MultiReader giving them a small performance boost.

ENGINE-1068 Less chatty JSON encoding of the dollar sign¶

Dollar signs in JSON strings were encoded as \u0024 instead of $. This change does not affect compatibility for consumers of any API other than to reduce the size of payloads that contain dollar signs.

ENGINE-1067 Do not store duplicate _id field in item properties¶

When storing the properties for an item the engine no longer includes a copy of the identifier as _id. It has always filtered out reserved properties (those that begin with an _) but previously used to store a duplicate copy of the id with the properties. This reduces storage requirements a little.

Any APIs that return properties which include _id remain unchanged, the engine dynamically includes this extra property to avoid any compatibility issues.

ENGINE-1065 Adds compressed response support to all API endpoints¶

All API endpoints can now generate gzip compressed responses. This impacts a handful of internal endpoints used to drive the admin interface and the following documented endpoints:

• /ws/didyoumean/{id}
• /ws/item/{id}
• /ws/items

The response will be compressed if the Accept-Encoding request header contains the value gzip.

ENGINE-1066 Use sparse bitsets at search time¶

The engine now uses sparse bitsets when appropriate for query time scratch space and when applying facets. This optimization improves the speed and memory use of some queries.