vrajat opened a new issue, #15639: URL: https://github.com/apache/pinot/issues/15639
- Server tenants are not applicable to logical tables as they do not contain any data. - Broker tenants are applicable as query execution on logical tables will use resources on the broker especially for aggregation in SSE queries. - If broker resources have to be isolated for queries on a logical table, then a broker tenant should be specified for that logical table. If not specified, default tenant (DefaultTenant) would be used. - A tenant will NOT be determined from the physical table list. This is because broker resources are not being used to process data from any one of those tables. Rather the result is a combination of data from all the physical tables of the logical table. - Note that physical tables in a logical table can have non-intersecting server tenants. The broker will send query requests and aggregate the responses from all the servers. - The broker tenant would be stored in the IDEALSTATES/brokerResource node as mapping of table name and broker nodes. These updates would transition to EV state by helix manager. - This enables the existing broker selector to choose broker nodes seamlessly with minimal code changes. -- 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-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
