fix(test): Force usage of ReadAPI #3625
Merged
+10
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes googleapis/java-bigquerystorage#2764
Related issue: #3574
SDK still uses the old API and just skips ReadAPI, even if it's enabled.
This happens because of this check:
java-bigquery/google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/ConnectionImpl.java
Line 1201 in 08c483c
In order to use ReadAPI, we need to add any of these configurations, for example, setJobTimeoutMs.
After this, we will see
Not Using Fast Query Path, using jobs.insert
andUsing BigQuery Read API
instead ofUsing Fast Query Path
.After enabling ReadAPI we've got 6-10x speed improvement: