afs_search_deploy - AFS - Reference Guides

AFS Filters Description

Product
AFS
AFS_Version
7.12
Category
Reference Guides
language
English

The afs_search_deploy filter is in charge of deploying reply databases (search and RTE, generated respectively by the filters afs_search_build and afs_rte_build) to the Update Manager.

The filter is declared with the afs_search_deploy type. It is in the antidot-paf-misc package. It is a visitor filter.

This filter will only work if instanced after the afs_search_build filter.

This filter can be instantiated only once at any given moment. It will not read the "instances" parameter in the configuration.

The Search Deploy filter specifications are described in the following table:

Parameter name

Mandatory

Type

Default

Description

min_sanity

No

integer

No check

Minimum value required in order to deploy reply database. Sanity = [ number of valid documents (EOL) * 100 ] / [ total number of documents (EOL, KO and FAILED) ]

min_documents

No

integer

No check

Minimum number of valid documents in whole database.

It takes all the updated data in $AFS7/result and sends only the necessary data:
  • For a first time indexing, all the files in $AFS7/result and in $AFS7/result/X (where X is the database number) are deployed.
  • For an incremental indexing, all the files in $AFS7/result and all the new files in $AFS7/result/X (where X is the database number) are deployed.

Note: This filter will not work if the service ID of the PaF is set to 0.
Note: This filter will only work if instanced after afs_search_build and afs_rte_build filters.
Attention: This filter can be instantiated only once at any given moment. It will not read the "instances" parameter in the configuration.
Attention: This filter needs Update Manager to be correctly configured in the server cloud and an afs_host binary on the indexing server. See Update Manager for more information.

This filter will not work if service ID of the PaF is set to 0.