Apache Pinot

this may be a bit of a stretch - i am running pinot with docker locally and trying to connect to it via jdbc and getting a SQLException

the query is simple - just a `select count(*) from ...` deal

but i am seeing this in the stack trace: `connection timed out: /172.17.0.2:8000`

i presume that's the docker container's address

:flushed: i forgot about that, but will try it now

that would be something like this, right?
```curl -H "Content-Type: application/json" -X POST -d '{"sql":"select count(*) from PatronEvent"}' <http://localhost:8000/query/sql>```

i think you may have nudged me in the right direction - the broker is on that port, but the docker image i used to start this doesn't expose it

but i do not understand why it is looking at that ip address (i am obviously new to pinot and learning the basics still)

I am not familiar with jdbc. But from the superset doc page it seems to need to be able to talk to broker and controller simultaneous

yeah, it seems like it needs both addresses and ports to be available - i will dig into it more tomorrow; thanks for the hints on that!

<@UK6JD1E85>, that was it; i made a new docker compose app and now it's working (i was using the quickstart, and that was not)

so that i's progress! i can run jdbc queries from a simple class and that is good; now i am trying to use datagrip and getting stymied :slightly_smiling_face:

```DBMS: APACHE_PINOT (ver. 0.10)
Case sensitivity: plain=exact, delimited=exact
Driver: APACHE_PINOT_DRIVER (ver. 1.0, JDBC4.0)
Effective version: UNKNOWN (ver. 1.0)
java.sql.SQLException.```
that is the only hint i see so far from datagrip; not exactly helpful, but there have to be some logs here somewhere

i've never use datagrip before so I am not 100% sure. but definitely not debuggable without logs

yeah, i'll send a support request to them, the pinot side of things seems to be happy (curl works, jdbc works, the web query console works), but datagrip is not so happy