The following procedure demonstrates a basic configuration that indexes all documents into a Vertica database.
However, you can customize the indexing process. For example, your CFS might be importing files from a File System Connector, e-mail messages from Exchange, and social media content. You might want to index these items into separate flex tables. To do this, you could run a Lua script to set the AUTN_INDEXER_SECTIONS
field in each document, and create a separate indexing operation for each type of content.
To configure CFS to index documents into Vertica
In the [Indexing]
section, use the IndexerSections
parameter to specify the names of the sections that contain indexing settings. If this parameter is already set, add the name of the new indexer to the list. For example:
[Indexing]
IndexerSections=IdolServer,Vertica
Create a new section in the CFS configuration file, with the same name that you specified in the IndexerSections
parameter. In the new section, set the following parameters:
IndexerType
|
The type of index to index documents into. Set this parameter to Library . |
LibraryDirectory
|
The directory that contains the library to use to index data. |
LibraryName
|
The name of the library to use to index data. You can omit the .dll or .so file extension. Set this parameter to verticaIndexer . |
ConnectionString
|
The connection string to use to connect to the Vertica database. |
TableName
|
The name of the table in the Vertica database to index the documents into. The table must be a flex table and must exist before you start indexing documents. For more information, see Prepare the Vertica Database. |
For example:
[Vertica] IndexerType=Library LibraryDirectory=indexerdlls LibraryName=verticaIndexer ConnectionString=DSN=VERTICA TableName=my_flex_table
For more information about these parameters and other parameters that you can set to customize the indexing process, refer to the Connector Framework Server Reference.