Content Type - Submit Indexing Job

The Job Size property controls how many documents are grouped together in a single indexing job.

• Set a lower value to create smaller, more frequent jobs, which may improve responsiveness and reduce resource contention.
• Set a higher value to process more documents per job, which may improve throughput for large-scale indexing.

Usage Guidance

• Adjust this value based on the size of your document set, available processing resources, and desired job granularity.
• Typical values range from 1,000 to 10,000, depending on system capacity and workload.

> Example:
> - For rapid feedback or testing, use a small value (e.g., 1000).
> - For production-scale indexing, use a larger value (e.g., 5000 or 10000).

The Priority property determines the execution priority of indexing jobs in the processing queue.

• Higher values indicate higher priority, causing jobs to be processed sooner relative to other queued jobs.
• Lower values may delay job execution if the queue is busy with higher-priority tasks.

Usage Guidance

• Increase priority for urgent or time-sensitive indexing operations.
• Use default or lower priority for routine or background indexing.

> Example:
> - Set to 5 for urgent reindexing after a major update.
> - Use the default value (3) for regular maintenance.

The Processing Queue property specifies which Processing Queue will execute the indexing jobs.

• Select a queue that matches your desired resource allocation and scheduling requirements.
• Use a dedicated queue for indexing to avoid contention with other high-priority tasks.

Usage Guidance

• Choose a queue with sufficient capacity to handle the expected indexing workload.
• Coordinate with system administrators to ensure the selected queue is available and properly configured.

> Example:
> - Use the default queue for most scenarios.
> - Select a custom queue for large-scale or isolated indexing operations.

The Reindex All property controls whether all documents are reindexed, regardless of whether they have changed.

• Set to true to force a full reindex, ensuring that all documents are updated in the search index.
• Set to false to only index documents that have been added or modified since the last indexing operation.

Usage Guidance

• Enable this option after making changes to extraction logic, document structure, or Indexing Behavior settings.
• Disable for routine incremental indexing to improve efficiency.

> Example:
> - Enable when switching to a new search schema or after a major data update.

The Detect Orphans property controls whether the command will search for and remove orphaned entries from the search index.

• Orphaned entries are index records that no longer correspond to any document in the repository.
• Enabling this option helps maintain index accuracy and prevents stale or invalid search results.

Usage Guidance

• Enable when cleaning up after document deletions, reclassifications, or migrations.
• Disable for routine indexing to reduce processing time.

> Example:
> - Enable after a batch of documents has been deleted or moved out of the Content Type.

A combination of the following flags:

The IndexOperations enumeration specifies which actions the Submit Indexing Job command will perform on documents in the search index. Multiple values can be combined using bitwise flags to tailor the indexing job to your needs.

Usage Guidance

• Select only the operations required for your scenario to optimize performance and resource usage.
• Use 'All' for comprehensive reindexing or maintenance.

> Note: The choice of operations directly affects which documents are added, updated, or removed from the index.

The Indexed Documents property displays the total count of documents that are currently present in the search index for the selected Content Type. This value reflects the current state of the index, including all documents that have been successfully added and are available for search and retrieval.

Use this property to monitor index growth, verify successful indexing operations, and assess overall index health.

The Added Documents property shows how many documents are pending addition to the search index. These are documents that exist in the repository but have not yet been indexed for the selected Content Type.

This value helps you track the backlog of unindexed documents and estimate the workload for upcoming indexing jobs.

The Updated Documents property indicates the number of documents that require updates in the search index. These documents have been modified since their last indexing operation and need to be re-indexed to ensure the index reflects the latest content and metadata.

Use this property to monitor the volume of documents that will be affected by update operations and to plan reindexing activities accordingly.

The Deleted Documents property displays the count of documents that should be removed from the search index. These may include documents that have been deleted from the repository or are otherwise considered orphaned in the index.

This value is useful for identifying and cleaning up stale or obsolete index entries, helping to maintain index accuracy and prevent invalid search results.