Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service Applications
  10. Interactive Data Preparation Service
  11. Enterprise Data Preparation Service
  12. Informatica Cluster Service
  13. Mass Ingestion Service
  14. Metadata Access Service
  15. Metadata Manager Service
  16. Model Repository Service
  17. PowerCenter Integration Service
  18. PowerCenter Integration Service Architecture
  19. High Availability for the PowerCenter Integration Service
  20. PowerCenter Repository Service
  21. PowerCenter Repository Management
  22. PowerExchange Listener Service
  23. PowerExchange Logger Service
  24. SAP BW Service
  25. Search Service
  26. System Services
  27. Test Data Manager Service
  28. Test Data Warehouse Service
  29. Web Services Hub
  30. Application Service Upgrade
  31. Appendix A: Application Service Databases
  32. Appendix B: Connecting to Databases from Windows
  33. Appendix C: Connecting to Databases
  34. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Search Index

Search Index

The Search Service performs each search on a search index instead of the Model repository or profiling warehouse. The search index enables faster searches and searches on content from the Model repository and profiling warehouse.
The Search Service generates the search index based on content in the Model repository and profiling warehouse. The Search Service contains extractors to extract content from each repository.
The Search Service contains the following extractors:
Model Repository extractor
Extracts content from a Model repository.
Business Glossary extractor
Extracts business glossary terms from the Model repository.
Profiling Warehouse extractor
Extracts column profiling results and domain discovery results from a profiling warehouse.
The Search Service indexes all content that it extracts. The Search Service maintains one search index for all extracted content. If a search index does not exist when the Search Service starts, the Search Service generates the search index.
During the initial extraction, the Search Service extracts and indexes all content. After the first extraction, the Search Service updates the search index based on content that has been added to, changed in, or removed from the Model repository and profiling warehouse since the previous extraction. You can configure the interval at which the Search Service generates the search index.
The Search Service extracts and indexes batches of objects. If it fails to extract or index an object, it retries again. After the third attempt, the Search Service ignores the object, writes an error message to the Search Service log, and then processes the next object.
The Search Service stores the search index in files in the extraction directory that you specify when you create the Search Service.