Yes, there is a limit to document indexing within RChilli’s services, particularly in the context of the Search & Match API, where documents are temporarily indexed for matching purposes. Here's a detailed breakdown:
📌 1. Parsing vs. Indexing Limits
-
Resume Parser API:
There is no long-term storage or indexing. RChilli does not store data parsed via the Resume Parser API. Parsed data is delivered in real-time as a response, and it's the client’s responsibility to store it if needed. -
Search and Match API:
Documents are indexed temporarily in a secure environment. These indexed documents are used for advanced matching and searching features.
📦 2. Indexing Capacity & Management
-
While there is no explicit public document stating the maximum number of documents that can be indexed, indexing large volumes is fully supported as RChilli is designed to scale.
-
However, indexed documents are not permanent and can be manually deleted using the
DeleteAllDocuments
API when needed:
🔐 3. Data Security & Region-Based Indexing
-
Indexing is region-specific (e.g., US, EU, SG), meaning data is stored securely in the selected region’s infrastructure.
-
Users can select the data center during setup for optimal performance based on location.
🧩 4. Combined Operations
-
If you wish to parse and index at the same time, RChilli offers the ParseAndIndex API, allowing both actions in one call.
-
Parsed data is not stored unless explicitly indexed.
-
For searchability, indexing is mandatory.
-
✅ Best Practice
If you need to manage large-scale indexing:
-
Use the bulk parsing and indexing capabilities.
-
Regularly clean your index using the delete APIs to maintain performance.
-
Reach out to support@rchilli.com if you expect unusually large volumes and need performance tuning or scaling advice.
Comments
0 comments
Please sign in to leave a comment.