This is only applicable to the CyborgDB SDKs. The REST API is stateless, so you don’t need to load indexes explicitly.
You must provide the exact same index key and configuration that was used when the index was originally created.
For production use, we recommend that you use an HSM or KMS solution for key management.
For more details, see Managing Encryption Keys.
Key Points
- Same Method: Service SDKs use
createIndex()
for both creating new indexes and connecting to existing ones - Exact Match Required: The index key and configuration must exactly match the original
- Automatic Detection: The service automatically determines whether to create or connect based on the index name
- No Separate Load Method: Unlike embedded SDKs, service SDKs don’t have a separate
loadIndex()
method
Index Caching
Index caching is handled automatically by the CyborgDB service. The service optimizes performance through:- Automatic Caching: Frequently accessed indexes are cached automatically
- Smart Eviction: Least recently used indexes are evicted when memory is needed
- Server-Side Optimization: No client-side cache configuration required