Hey guys, sorry to ask something about Trino here,...
# troubleshooting
d
Hey guys, sorry to ask something about Trino here, but it's related to Pinot and unfortunately I couldn't get help from anyone at their community. I'm doing an experiment with Trino and Pinot, and I noticed that a query I do to different tables in Pinot ends up with Trino actually querying all of the existing segments in Pinot, completely bypassing any partitioning I defined for my tables. Is this expected? Has somebody here ever experienced this as well, but solved it? I'm thinking about using dynamic tables in Trino to work around that issue, but it just feels dirty to have to do that...
k
whats the query? @User can provide more info.
d
Sorry for the delay; Here's an example query I run, which involves querying inside a specific period of time, but Trino bypasses that and instead queries all segments regardless of the dates:
Copy code
select distinct weight from weights
  inner join brands_metrics on weights.pmxid = brands_metrics.pmxid 
  inner join filters on weights.pmxid = filters.pmxid
where
  brand_id = 1000226 and
  filters.name = 'gender' and
  contains(filters."values", 2) and
  weights.date > 20130501 and
  weights.date < 20130515 and
  brands_metrics.date > 20130501 and
  brands_metrics.date < 20130515 and
  filters.date > 20130501 and
  filters.date < 20130515
here,
brands_metrics
,
weights
and
filters
are all tables that contain a
date
column set as the time column upon table creation.
👀 1