Migrating Custom Property Extractors That Are Defined Prior to Service Pack 1
Applies to: SharePoint Server 2010
In this article
Verify Your Migration Requirements
Migration to the New Configuration File Format
Property Extractor Configuration Using optionalprocessing.xml
Verify Your Migration Requirements
You only need to consider a migration if you have defined custom property extractors in optionalprocessing.xml. There are two migration alternatives, as follows:
Do not change the existing configuration, but add new property extractors in CustomPropertyExtractors.xml.
Select this alternative if you do not want to change the existing configuration, and do not have any additional requirements to the existing property extractors.
For this alternative, you do not need to modify the existing crawled property mapping for these property extractors.
To create new property extractors, follow the steps in Creating a Custom Property Extractor.
Perform a migration of existing property extractors to the new configuration format. Follow the steps in Migration to the New Configuration File Format.
Migration to the New Configuration File Format
If you have an existing property extractor configuration that uses one of the processing stages in optionalprocessing.xml, you can perform a migration to the new configuration format.
To migrate a property extraction configuration
Disable the custom property extraction stage in optionalprocessing.xml. Change the active attribute value to no.
Remove the crawled property mapping for the crawled property associated with this stage. For information about crawled property names, see Property Extractor Configuration Using optionalprocessing.xml.
Create a new property extractor. Follow the steps in Creating a Custom Property Extractor.
Make sure that you map the generated crawled property to the same managed property as the existing property extractor.
You do not need to make any other changes to the managed property configuration or the associated refiner configuration.
You do not need to re-crawl content unless you have extended the property extraction dictionary or use one of the new case-insensitive property extractor types.
Property Extractor Configuration Using optionalprocessing.xml
Note
The following configuration option is no longer recommended after you have installed Service Pack 1. It is supported for backward compatibility, and you can keep your existing property extractor configuration if you do not have to modify it.
In <FASTSearchFolder>\etc\config_data\DocumentProcessor\OptionalProcessing.xml, you can define up to three custom whole-word matching property extractors and two custom word-part matching property extractors. You use one of the predefined item processing stages named wholewordsextractor1, wholewordsextractor2, wholewordsextractor3, wordpartsextractor1 and wordpartsextractor2.
Each custom property extraction stage has an associated crawled property and property extraction dictionary.
Table 1 shows the relation between the available property extractors, the crawled property, and the file name for the property extraction dictionaries in the resource store.
Table 1. Relationship between extractor name, crawled property, and file name in resource store
Extractor Name |
Crawled Property |
File Name in Resource Store |
|---|---|---|
wholewordsexstractor1 |
wholewords1 |
wholewords_extraction1.xml |
wholewordsexstractor2 |
wholewords2 |
wholewords_extraction2.xml |
wholewordsexstractor3 |
wholewords3 |
wholewords_extraction3.xml |
wordpartsexstractor1 |
wordparts1 |
wordparts_extraction1.xml |
wordpartsexstractor2 |
wordparts2 |
wordparts_extraction2.xml |
See Also
Concepts
Creating a Custom Property Extractor
Linguistic Dictionary Schema (FAST Search Server 2010 for SharePoint)
Query Refinement (FAST Search Server 2010 for SharePoint)