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

BigQuery Node not processing results pagination correctly #9739

Closed
imReker opened this issue Jun 14, 2024 · 3 comments
Closed

BigQuery Node not processing results pagination correctly #9739

imReker opened this issue Jun 14, 2024 · 3 comments
Labels
in linear Issue or PR has been created in Linear for internal review Released

Comments

@imReker
Copy link

imReker commented Jun 14, 2024

Bug Description

I'm using BigQuery to get a lot of data. Because the result json > 5MB, so BigQuery paginates the results.
But n8n only fetched and parsed first page of data and ignored the rest.

To Reproduce

  1. Create a BigQuery node.
  2. Make a query to generate large data results, such as 1000 rows of strings with size of 1KB.
SELECT id, "aaaaaaaaaaaaaaaaaaaaaaaaaaa......  1KB of string" as `d`
FROM UNNEST(GENERATE_ARRAY(1, 1000)) AS id
  1. Execute and only get about 800 rows in result, not 1000 rows.
  2. Set Raw Output to true and execute the query, I noticed that there is pagination token, means the rest of data is in next page.
    image

Expected behavior

Fetch pagination data correctly.

Operating System

Ubuntu 24.04

n8n Version

1.45.1

Node.js Version

v20.14.0

Database

MySQL

Execution mode

main (default)

@imReker
Copy link
Author

imReker commented Jun 14, 2024

According to Google's document https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs/query#QueryRequest

A non-empty pageToken indicates that additional results are available. To see additional results, query the jobs.getQueryResults method. For more information, see Paging through table data.

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Jun 17, 2024
@Joffcom
Copy link
Member

Joffcom commented Jun 17, 2024

Thanks for reporting this @imReker, I have created NODE-1417 as the internal ticket to get this fixed.

@janober
Copy link
Member

janober commented Jul 31, 2024

Fix got released with [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review Released
Projects
None yet
Development

No branches or pull requests

3 participants