Microsoft Enterprise Search Blog

PingBack from http://www.artofbam.com/wordpress/?p=5258

Hi,

I have some queries on MOSS Search, specifically related to crawling and indexing. Would be great to have your inputs on these:

-Is there a hard limit of having only one IFilter per file extension? For e.g. in our MOSS Search server, I can see that the ‘.txt’ IFilter seems to be implemented in ‘tquery.dll’. Can I have an additional IFilter say, ‘MyTxtFilter.dll’ that chains along with this default filter? (So that both would be called by the filter daemon when indexing).

-If the above is not possible then is there a way for me to have my custom code execute with the default IFilters? If so, how? I am specifically looking for ways to access chunks at crawl time and assign text or value inside those chunks to my custom created crawl properties.

-If we have to necessarily have only one IFilter per file extension, can I replace the default shipped IFilter with my custom created IFilter (i.e. replace tquery.dll with MyTxtFilter.dll)? An assumption I am making here is that since we are not messing with the protocol handlers, my custom IFilters will get chunks with text or values inside for all the content that the indexer crawls (and has protocol handlers registered for). What is the behavior that I will see after each crawl ends (apart from seeing only those crawl properties that MyTxtFilter.dll creates)?

-Say on a MOSS Server, I have two search SSP’s configured to crawl the exact same content. Let these search services be SSP1 and SSP2. Can I map crawl properties from SSP2 to managed properties in SSP1? (SSP1 would therefore have managed properties that are mapped to crawled properties from both SSP1 and SSP2). I am not able to explicitly see crawled properties of other SSP's in the mapping page. Can it be done programmatically? Are there any caveats that I need to be careful about?

Rgds,

Sushrut.