You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2021/07/08 16:46:17 UTC

[GitHub] [incubator-pinot] johighley edited a comment on issue #7138: Support for Tenant data isolation

johighley edited a comment on issue #7138:
URL: https://github.com/apache/incubator-pinot/issues/7138#issuecomment-876556994


   Mayank created this request after our Slack conversation, so to expand the use case:  We have a lot of clients (tenants) and require data separation. Each client will have the same set of tables (ex: customer, account).  We need the ability for each tenant to have the same set of tables without requiring unique table names.  
   
   Some way to indicate the tenant for operations would be needed:  select * from TenentA.accounts; for example
   
   It would also be helpful if brokers and servers could host multiple tenants.  Otherwise, the number of brokers and servers needed (with redundancy) grows very quickly.
   
   I think the disconnect may be that Pinot sees tenants as being different applications, each with distinct table names.  Many use cases, though, treat tenants as different clients, all using the same application. Each client needs the same set of application tables but the tables need to be separated when data can't be co-mingled across clients.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org