GroupDocs.Search for Python via .NET indexes and searches documents of a wide range of supported document formats. Every task follows the same workflow: create or open an Index, add() documents to it, then search() it and read or highlight the results. The index lives in a folder of its own and is opened again on the next run, so documents are indexed once and searched many times. For details on a feature, follow the links to the Developer Guide.
Creating and opening indexes
Create an index on disk or in memory, open it again on the next run, load an index into memory completely or save it to another folder, and keep several indexes in a repository that searches them all at once. Settings chosen at creation decide what an index keeps: a normal, compact or metadata-only index, with or without the text of the documents, stored at a choice of compression. An index created by a previous version of the library can be updated to the current format. See Index lifecycle, Search index location, Search index settings, Search index repository, and Index format and compatibility.
Update an index to take changed, deleted and added documents into account, merge several indexes into one, and optimize an index to speed up search and to remove deleted documents physically. Delete documents by path or by key, tell the index about renamed documents so they are not reindexed, and check an index’s integrity and restore a damaged one. Index changes are atomic, and index data is protected by checksums. See Update index, Merge indexes, Optimize index, Delete indexed documents, Document renaming, and Checking index integrity.
Each index keeps the dictionaries its search uses - synonyms, homophones, stop words, aliases, the alphabet, character replacements, the spelling corrector and document passwords - and each can be read, changed, exported and imported from Python. See Managing Dictionaries.
Images and OCR
Calculate and index image hashes for reverse image search, which finds the documents that contain a picture like a given one. The text of images and scans is indexed through an OCR engine you connect. See Reverse image search and OCR support.
Events and Python callbacks
Index events report what an index does and let a handler take part: follow indexing progress, skip a document, or supply a password as a document needs it, with index.events.file_indexing += handler. Text extractors, OCR connectors, loggers and word form providers are plain Python classes or functions that the engine calls. See Search index events, Logging, Indexing reports, and Word forms provider.
Performance and concurrency
Searches are thread-safe and run while documents are indexed, updated, deleted, merged or optimized; one search can also use several threads. See Search thread safety and Search options.
Scaling
A search network distributes the documents over shards on several nodes and balances indexing and search across them. See Scaling.
On-premise
GroupDocs.Search for Python via .NET runs entirely on your own infrastructure - your documents never leave your environment. The package is a self-contained wheel that bundles everything it needs, so no Microsoft Office, OpenOffice, or separate runtime has to be installed. See System Requirements for the supported platforms and native dependencies.
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.
On this page
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.