snleee opened a new issue #4273: Table Level Tenant Isolation URL: https://github.com/apache/incubator-pinot/issues/4273 There has been an increase in demand for sharing commonly used data (or table) among multiple different site facing use cases. Due to strict latency SLA of site facing use cases, we usually assign each use case to a different tenant for resource isolation. If multiple use cases want to share the same data, we currently have to provision exactly the same table and set up the separate flow for data ingestion. As clearly seen, the current approach has many disadvantages: more manual work during the onboarding process, the increase in the chance of data inconsistency among tables due to separate data ingestion flows, and a waste of resources (data duplication). In order to support such use cases efficiently, we should improve the current approach while supporting the following requirements: - **Performance Isolation:** One use case should not impact performance of other use cases. - **Effortless onboarding:** New use case built on top of the existing table should be able to set up with the minimum effort (no new data flow). - **Data consistency:** Results of the same query should be the same across all use cases. - **Independent quota enforcement:** Each use case can have different SLAs (qps, latency). We should be able to enforce the quota independently. - **Independent monitoring:** We should be able to monitor each use case separately.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
