big fan of memgraph, been utilizing for awhile over neo4j ever since I saw a NASA article detailing their migration effort and the why behind it.
my question is does this multi-tenancy support apply to vector embedding as well? from usage I know it supports vector indexes on nodes/edges, I’m curious whether those embedding properties and vector indexes are isolated and manageable per database in a multi-tenant deployment? any limitations I should know about? context: individual/organization/enterprise knowledge bases being developed need mechanism to promote relevant information up from personal stores into team and from team into corporate.
big fan of memgraph, been utilizing for awhile over neo4j ever since I saw a NASA article detailing their migration effort and the why behind it.
my question is does this multi-tenancy support apply to vector embedding as well? from usage I know it supports vector indexes on nodes/edges, I’m curious whether those embedding properties and vector indexes are isolated and manageable per database in a multi-tenant deployment? any limitations I should know about? context: individual/organization/enterprise knowledge bases being developed need mechanism to promote relevant information up from personal stores into team and from team into corporate.