You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data for the tenant is isolated within this set of schemas (we currently query what we need by using search_path dynamically)
So our partitioning requirements are simple looking at it one way. Assuming we have three nodes, as long as we ensure that a new tenant's schemas all fall into a single node we should be good. New tenants can be onboarded to an existing node with some hashing mechanism
Or does it? Any workaround to support this mechanism? We don't want to mess with our multi tenancy approach by moving to monolith tables is a tall order at this time
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So our multi tenancy is like this:
search_path
dynamically)So our partitioning requirements are simple looking at it one way. Assuming we have three nodes, as long as we ensure that a new tenant's schemas all fall into a single node we should be good. New tenants can be onboarded to an existing node with some hashing mechanism
But it appears Citus doesn't support this based on what I've seen here: https://docs.citusdata.com/en/v10.2/
Or does it? Any workaround to support this mechanism? We don't want to mess with our multi tenancy approach by moving to monolith tables is a tall order at this time
Beta Was this translation helpful? Give feedback.
All reactions