Skip to content

Logical separation for stores #319

@deven96

Description

@deven96

A good quality of life improvement would be getting a form of "schema" support for ahnlich. Today, we have a flat namespace:

  • All stores exist in a single global namespace
  • Store name: "embeddings", "user_vectors", "test_store"
  • No organizational hierarchy
  • No logical separation between different use cases

Example current usage

# All in same namespace
CREATESTORE user_embeddings DIMENSION 512
CREATESTORE product_embeddings DIMENSION 512
CREATESTORE test_embeddings DIMENSION 512
CREATESTORE dev_user_embeddings DIMENSION 512

Benefits of Schema Support

  1. Logical Organization. Gives room for multitenant applications, functional and environment separation
  2. Name collision prevention. Two teams cannot use embeddings as store name.
  3. Bulk operations. We would be able to drop one entire schema without affecting the rest or list stores per schema
  4. In the future we can have access control where we grant permissions on a per-schema basis

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions