This message was deleted.
# troubleshooting
s
This message was deleted.
r
Hi Shubham! I locally tried a small experiment and was able to connect
trino-402
installation with my local druid setup. I followed the steps mentioned in https://trino.io/docs/current/connector/druid.html My druid setup was the latest apache master. Which druid version are you using?
s
Hi Rohan I am on the latest master branch. Are you using it via bearer auth ? Can you share you are setting the config.
r
I was using un-secured setup for the connector. The properties were :
Copy code
connector.name=druid
connection-url=jdbc:avatica:remote:url=<http://localhost:8888/druid/v2/sql/avatica/>
8888
was my local router are you using some authentication setup as well?
s
Yes I am using the basic authentication in druid but wasn't able to connect with that.
I think the doc is also not updated that well. Are you seeing the catalog name as druiddb as mentioned in the doc ? https://trino.io/docs/current/connector/druid.html
r
yeah, I think that's a mistake in the docs. the catalog name should be
druid
in the docs
also I can try to check the basic auth setup as well
s
Thanks Rohan let me know if it works.
r
I tried basic authentication and was successfully able to connect. For druid side auth, I followed https://druid.apache.org/docs/latest/development/extensions-core/druid-basic-security.html and on the trino side added the
connection-user
and
connection-password
properties in the catalog properties
s
Were you able to query the tables also ? For some reason I am always getting org.apache.http.client.ClientProtocolException.
r
Yes I was able to query the tables too. is there more info in the exception you see? maybe in the trino log files? Also, are you able to query druid independently?
s
Hi Rohan as below you can see, what i am facing is that a simple query is running in my local for more than 30 minutes, seems like this is stuck and no logs in the trino container. I am running this in a dockerized container.
For delta catalog I am able to query. This is happening only for druid catalog.
Also in the console all i see is WAITING_FOR_RESOURCES while executing any simple query.
r
Thanks for the update! Is your druid cluster also in the same container as the trino deployment? Also, are you able to query druid directly ie without trino?
s
The druid is hosted via imply for us. So we are able to query druid. I am running trino in my local docker container.
r
I tried connecting with an imply managed hybrid cluster as well and was able to do it. The steps I followed were : 1. Download the
Root certificate
from Imply's API page and create a java truststore from it 2. Add the truststore in the jdbc url using the following format :
Imply-Private-JDBC-connection-string;truststore=<path-to-truststore-file>;truststore_password=<truststore-password>
(ref : https://calcite.apache.org/avatica/docs/client_reference.html - druid uses calcite avatica for JDBC driver). Also added user/password from the Imply API page in the trino catalog properties 3. Connect to the VPN where the druid cluster is before running trino queries Were you also following a similar way to connect to druid? A couple of things to check outside druid could be : 1. your docker container does allow outside connection 2. your trino container has both coordinator and worker configured in it. a lot of times
waiting-for-resources
in trino could also mean no workers available I hope that helps!
s
Thanks Rohan It worked. 😄
r
Great news! 😄