https://pinot.apache.org/ logo
Join Slack
Powered by
Hi, I'm trying to use the Trino/Pinot connector bu...
# troubleshooting
t
Hi, I'm trying to use the Trino/Pinot connector but I'm seeing some strange behavior. Queries such as 
select * from pinot.default.table
seem to just run forever without returning any results. But queries like 
select max(col) from pinot.default.table
seem to run fine. It looks like I have to do some sort of aggregation or group by in order for the query to run. I can't seem to just select rows. Is this behavior expected?
m
@Xiang Fu ^^
x
have you tried ran with a limit X for your select * query?
t
yep I've tried with a limit
As another example: 
select col from pinot.default.table limit 10
seems to run forever without returning. 
select col from pinot.default.table group by col limit 10
works
Actually this seems to be fixed after upgrading trino
a
@Tiger Zhao Can you confirm if you observed this using Pinot > 0.8 with Trino version older than 365?
t
Yes I was on the latest version of Pinot and a Trino version < 365.
a
Got it. Thanks for confirming.
cc: @Elon can we introspect Pinot version from Trino connector code? If so we should add guards to prevent using >=365 on older Pinot brokers (but cannot prevent the other way around now since that ship has sailed) to prevent cases where it doesn't fail but just returns incorrect results? Or does 0.8 Pinot client already complain if connecting to older brokers?
e
We can definitely check the version. For pinot compatibility, I'm not sure what the compatibility matrix is for pinot0.8.0. So the issue was that limit was being ignored in a pinot query?
Is there an issue for it? We can definitely do this.
a
I'll create one and take a shot at it. Any pointers on how I can get hold of the version information?
e
Nice! There's an api call in the controller:
it's just 
/version
i.e. <controller url>/version
👍 1
lmk I can help to review it
👍 1
3 Views
Open in Slack
PreviousNext
Powered by