jadami10 opened a new issue #8061:
URL: https://github.com/apache/pinot/issues/8061
If you have a table with the following config:
```
tenants:
broker: "TenantA"
server: "TenantB"
```
The `/instance/BROKER_` page will not show your table.
The `/tenants` page will not show your table (though maybe this is ok since
server tenant maybe takes more priority here)
I started trying to tackle this by doing `/v2/tenants/{tableName}/tables`
where it would return `{"server": [table1, table2], "broker": [table1,
table3]}`, but I stopped. There just seems to be a disconnect between how
tenants are designed, how they might be used in practice, how the API serves
you data, and how the UI displays them.
The UI seems to make the assumption everywhere that server tenant == broker
tenant. The `getTenantTable` function and backing API and all their users only
ever get the tables for that tenant served by the server. There's no good API
for tenant -> broker -> table. There is `/brokers/tables`, but again the UI is
a little weird because it uses the same `InstanceDetails` page for both brokers
and servers. So using a completely different function depending on instance
type will look weird.
Anyway, I'm happy to work on this if anyone has an opinion on the
implementation. I just don't have the time right now to chase figuring out the
desired approach.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
