File share connector release notes

File share connector 2.1.0.0

This release of the File share connector features the following enhancements. For more information about the connector, see About the File share connector.

System Enhancements

Feature Description
Indexing enhancements

The File Share connector can now detect permission changes on files or folders during 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. and force those documents or files to be re-indexed. The file share connector uses the following logic when determining what items to reprocess:

  • If the permissions change on a folder, the entire folder and all its sub-folders and files are reprocessed.

  • If the permissions change on a document, the document is recrawled.

The File share connector will detect the following permission changes:

  • If inheritance is broken from a parent.

  • If additional permissions are added on top of the inherited permissions.

  • If a specific permission on a file is changed to re-inherit permissions from a parent.

Crawling enhancements The File share connector now uses a retry mechanism that can detect failures during crawls and attempt to reconnect before producing an error. This enhancement improves the reliability of the connector and reduces the chance of premature failures.
Support for indexing large files When attempting to index files where the size of the file exceeds the Max File Size setting as specified in Connectivity Hub, the File share connector will now extract and index the 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. of those files, however, the content of these files will not be indexed.

Fixed issues

  • If the application pool account did not have access to the file share, the File share connector crawl would fail. (BAI-17641)

  • When the Skip Windows metadata setting in the connector configuration was unchecked, the Windows extended file property metadata was not included in the crawl results. (BAI-14959)