Hello Everyone,
I have installed pinot on k8 and c...
# troubleshootingj
Jatin Kumar
09/04/2022, 6:31 PMHello Everyone,
I have installed pinot on k8 and created two tenants(each for broker and server) with name
defaulttestdefaulttests
saurabh dubey
09/04/2022, 6:55 PMIf you're using pinot-java-client, AND your app is within the same subnet / vpc as your brokers, you can initialise your client with ZK URL. The client will use the ZK metadata to route the queries to the correct broker for a given table
j
Jatin Kumar
09/04/2022, 6:57 PMthanks @saurabh dubey, i am using superset tool to connect to pinot. any work around for this?
Jatin Kumar
09/04/2022, 7:41 PM@Xiang Fu any suggestions?
x
Xiang Fu
09/04/2022, 10:41 PM
right, I think that’s the limitation of python pinot client, it’s not really aligned with superset database concept
Xiang Fu
09/04/2022, 10:42 PM
you should directly query default namespace with your tables in the test tenant.
Xiang Fu
09/05/2022, 1:02 AM
Xiang Fu
09/05/2022, 1:03 AM
so pinot side will return all the schema as
defaultXiang Fu
09/05/2022, 1:06 AM
from pinot side, python client just hit all the pinot brokers, which can be any broker in any tenant, so you may fail at any time
Xiang Fu
09/05/2022, 1:09 AM
for now, you can have two solutions:
1. make only one broker tenant, so all the tables are sharing same tenant, and your pinot service will be the only entry point for all the queries.
2. Create a k8s service for each tenant, so that you will have pinot-default svc and pinot-test svc. Then from superset, you need to connect to two pinot entry point, same controller, but different broker endpoint. So you treat each pinot tenant as one data source.
Xiang Fu
09/05/2022, 1:10 AM
We are also working on making this experience more smooth by just giving the controller endpoint or proxy end point. However, it’s pretty hard with k8s set up as there are limited endpoints.
j
Jatin Kumar
09/05/2022, 5:06 AMthanks @Xiang Fu 🙏