ID ENCODING Federation Services uses the source repository id of a document as a default value for the id in ElasticSearch. These can sometimes contain illegal characters, especially if they are file paths, such as from a Filesystem or Amazon S3. As part of the indexing process, the value of this field will be encoded to ensure its validity. Currently, only slashes, spaces and apostrophes are encoded, but this will likely change to full encoding in the future to better support non-standard character sets. FILE CONTENT If Include Binaries is checked in the Details tab, the connector will convert it to a base64 encoded String and store it in the binaryData field
Note: ElasticSearch does not support writing of multiple versions of a document and will only write the latest one picked up in a migration. All other versions will be ignored instead of being audited and will not be counted as Skipped
- ID Attribute: The field that will be used to set the document id
-
Index Name: The name of the collection where the indexes will
be created.
- If the collection already exists and does not have the required mappings, Federation Services will attempt to update the mappings
- Batch size: The number of documents to generate before sending a request.
- Out Renditions as array to the renditionData field: If there are multiple renditions, they will be stored as a list of base64 encoded strings.
-
Term Vectors: Term vectors increase the size of an index but
are required for highlighting and More Like This searches.
- All text based default Federation Services fields are included by default
- Term vectors can only be applied to text fields.
- Term vectors will be enabled for any custom text field added to mappings