Output Specification:
- Collection: The name of the collection to create/write to. Federation Services will handle the “files” and “chunks” collections internally
- Insert Federation Services Metadata: Required for Federation. Write Federation Services metadata onto objects. Automatically included if GridFS is enabled in auth connection.
- Use bulk write operations (MongoDB only): Federation Services will use bulk write operations for better performance.
- Number of documents to write per bulk operations: Number of documents to send per bulk write
- Include Un-Mapped Properties: Add all metadata on the document
Advanced Options:
- Drop and Build Indexes: Indexes are created to speed up searches. This will rebuild them entirely. This can be a lengthy process and should only ever be performed on the initial run
- Index Keys: A comma delimited list of field keys to index. For multiple collections use key1:collection1,key2:collection2.
- Upsert Key: ‘Upserting’ is simply means “Update if exists”. This key will be checked to see if the document already exists. Leave blank to use Federation Services source repository key. If not set and Insert Federation Services Metadata is not checked, then only creates will be called.
- MongoDB Write Concern: Write concern describes the level of acknowledgement requested from MongoDB for write operations
- File Store Connector ID: Connector ID of Content Service Connector to use as the File Store. Or leave blank to use native GridFS. This field is only used if MongoDB GridFS is Enabled in the Authentication Connector.
Mango Repository:
- Comma delimited list of collections to crawl: As the name says.
- Select what field will act as the source id for the document: The field which will appears as the “source_repository_id” field in the output document
- Query: A Mongo Query. If left blank the query will be “{}”, or “get all”