hasura / hasura/graphql-engine

BigQuery JDBC does not do nested filtering correctly

Open
#10,796 0 comments 0 reactions 0 assignees View on GitHub
k/v3-bug t/data-connectors
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Component

### What is the current behaviour?

I have two datasets that I link by a string ID. They are both account tables, it is a one-to-one relationship (Object type).

They link correctly in that I can select nested fields and build a where query with nested field filtering. However, we run into a "row limit exceeded issue" even when I specify a limit of 10 or even a limit of 1. It seems as thought it's running the nested filter level query as a separate query, which if there resulting dataset is larger than 10,000 rows it will come back with an error.

### What is the expected behaviour?

It should be creating a simple LEFT JOIN and do the proper filtering and limiting.

### Screenshots or Screencast

Image
Image
Image

It does this query it seems first which is the problem, there is no limit applied:

Image

### Keywords

bigquery, ndc-jdbc, nested filtering

Contributor guide

Open the contributing guide

Research direction

Start by reproducing nested filtering through the BigQuery JDBC connector, using the generated query shown in the issue as the comparison point. Inspect the ndc-jdbc connector path and verify how nested filters and limits are translated. Done means the generated query applies the requested limit while filtering nested fields without triggering the row-limit error.

Written by the indexing model from the issue text.

Assessment

Tech stack
google-cloud, sql
Domain
backend-api-design, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.