Amazon S3 connector release notes

The respective releases of the Amazon S3 connector feature the following enhancements. For more information about the connector, see About the S3 connector.

Amazon S3 Connector 1.2.0.0

System Enhancements

Feature Description
User-defined metadata Provides context with details such as the source, type, owner, and relationships to other data sets. Metadata provides details around the item being crawled by Connectivity Hub. support

The Amazon S3 connector now supports the BinaryContentMetadata multi-value metadata field that contains user-defined metadata from the binary content file in JSON format. If your metadata file has multiple related binary content files, the metadata value will have a JSON record for each file. For example, BinaryContentMetadata: [{ “x-amz-meta-testkey”: “test”, “x-amz-meta-customMeta”: “test value” }]. Your metadata must be regenerated for the BinaryContentMetadata to be visible.

For more information, see Set Up and Configure the Amazon S3 Connector.

Fixed issues

  • Changes to the related documents index were not being included in incremental crawls Scanning and capturing only new data from all of your content sources. This data did not exist when the last crawl was run.. (1833361)

  • Crawl jobs with the Amazon S3 connector would fail if the crawled file names contained non-english characters. (1821134)

  • In some scenarios, when selecting types to include in a crawl, nested content types were not displaying in the hierarchical list of content types. (1776201)

  • After a full crawl, if an existing file was modified in the Amazon S3 bucket, the modifications were not picked up during the next incremental crawl.

  • When specifying the related documents pattern in the connector configuration, a NullReferenceException error was returned if all the available tags were not included.

Amazon S3 Connector 1.1.0.0

System Enhancements

There are no system enhancements in this release.

Fixed issues

  • Crawls using the Amazon S3 Connector would fail if the document path was more than 200 characters long. (BAI-17906)

  • The Amazon S3 Connector was not reading configuration parameters correctly, causing crawls to fail.(BAI-17698)

Amazon S3 Connector 1.0.3.0

System Enhancements

There are no system enhancements in this release.

Fixed issues

  • During some crawls with the Amazon S3 connector, certain documents failed with a "seek operation not supported" error. (BAI-16577)