Release Notes

Release Date: July 18th, 2023

What’s New

Our Binary Data Storage Service now integrates with Azure Blob Storage, providing you with even more flexibility and options for storing binary data. Our binary service is now fully compatible with all three major cloud providers: Google, Amazon, and Microsoft. We have also enhanced our Search UI by enabling it to display a greater number of results for featured snippets through a ‘Show More' option.

Feel free to contact our development team if you have any questions, suggestions, or feedback. We value your input and are committed to continuously improving our services. Continue to read on for all new features, bug fixes, and improvements.

New Features

Bugs Fixed

• Improvement in JsonUtils.substitute

• Token scanner writes checksums to the scan index.

• Staging Connector - Aggregation by group doesn't support Arrays

Improvements

• Add "Append" support for field mapper

• Update documentation for staging repository and connector

• Seed option to exclude "__pdp__" information in ingestions

• [Ingestion] Chunk processor - Handle documents with no sourceField

• [Discovery API] Set a min_doc_count in the Snap component for Mongo engine

• [Staging API] Handle max size error when querying an aggregation in Staging API

• Implement Tika Timeout

• MongoDB Atlas Connector: Add option to use aggregations as starting point

Breaking changes

• If upgrading from a version prior to 1.7.0, export the existing configuration, delete the configuration indices (ingestion: seed, processor, and pipeline / discovery: endpoint and processor), and re-import it after upgrade has been performed.

Others

• None

Supported Versions

Discovery provides support and bug fixing for the following versions:

• Version 1.8.0

  • If upgrading from a version prior to 1.7.0, export the existing configuration, delete the configuration indices (ingestion: seed, processor, and pipeline / discovery: endpoint and processor), and re-import it after upgrade has been performed.

• Version 1.7.0

  • Close record collector in AbstractRequestActionExecutor for errored jobs

  • Incorrect log message from Staging Hydrator

  • Error importing zip

  • [Discovery API] Feedback Atlas default template

  • [Ingestion] Possible memory leakage in Elasticsearch connector

  • ES Connector: Checksum is not hashed before adding a record.

  • Search UI showing more search result pages than required

  • Job in the wrong state should be retried

• Version 1.6.0 (If you are in this version, plan to upgrade soon)

  • Pipeline configuration should not allow null action

  • Ingestion Admin should allow deep cloning multiple times

  • Single seed schedules should not be enqueued if the same seed is already running

  • Discovery API - Endpoints should handle an empty body request

  • Discovery API - Mongo Component should store the response body as JsonNode

  • Discovery API - Snap Component not casting error message when facets field points to an array

  • Breaking changes:

    • When configuring the S3 connector, the region must be in the format AWS requires it.

      • e.g. “us-east-1” instead of “"US_EAST_1"

Deprecated Versions

Releases that are no longer recommended for use and their deprecation dates are listed below.

• Version 1.5.0 (July 2023)

  • Internal server should not error when adding item with no "body" to Staging repo

  • JsonUtils can not substitute value properties of intNode objects when are into an array

• Version 1.4.0 (June 2023)

  • Environment variables are not substituted in processors if there are no seed properties

  • Credentials Service cannot deserialize value '_id' from cache

  • Distilbert by HuggingFace Service causes node to reset

• Version 1.3.0 (April 2023)

  • Discovery API’s Post Component was failing to parse response from elastic

  • Prevent creation of seeds with duplicate name

  • Mongo credential source should default to “admin”

  • Failed to encode 'Credential'. Encoding '_id' errored with: Can't find a codec for class java.lang.Object

  • Import fails with unhelpful error message

  • Aggregation merge should support empty values and also others than just content