Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve predicate pushdown of nested fields on BigQuery struct type #10644

Closed
alexpusch opened this issue Jan 17, 2022 · 1 comment
Closed

Improve predicate pushdown of nested fields on BigQuery struct type #10644

alexpusch opened this issue Jan 17, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@alexpusch
Copy link

alexpusch commented Jan 17, 2022

Using Trino 368, configured with a BigQuery connector there is a significant performance impact while querying using a nested field.

Reproducible example:
public github archive big query connection:

connector.name=bigquery
bigquery.project-id=githubarchive
bigquery.credentials-file=...

fast query:

SELECT * FROM bigquery."day"."20220112" 
where id = '19687131707'
limit 1

very slow query:

SELECT * FROM bigquery."day"."20220112" 
where repo.id = 447018807
limit 1

Relates to https://trinodb.slack.com/archives/CGB0QHWSW/p1642075559152000

@alexpusch alexpusch changed the title Big query connectors poor performance for nested fields queries Big query connector poor performance for nested fields queries Jan 17, 2022
@ebyhr ebyhr changed the title Big query connector poor performance for nested fields queries Improve predicate pushdown of nested fields on BigQuery struct type Jan 17, 2022
@ebyhr ebyhr added the enhancement New feature or request label Jan 17, 2022
@hashhar
Copy link
Member

hashhar commented Oct 8, 2024

Improved with #23443

@hashhar hashhar closed this as completed Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

3 participants