Support limit pushdown in Bigquery connector #24021

krvikash · 2024-11-04T12:05:12Z

Description

Since BigQuery Storage API doesn't support limiting rows, but REST API supports LIMIT clause.
https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax#limit_and_offset_clause

So, We will be using REST API to read all kinds of table (view, MV, managed table, external table, snapshot table, ...) when limit is specified in the query.

Additional Context

I have tested the limit with a managed table with Rest API + limit pushdown and with Storage API without limit pushdown.

The Storage API without limit pushdown generally performs better in most cases. However, the REST API with limit pushdown is only slightly faster by about 1–2 seconds when the physical data size is very small, around 1 MB.

Table

  table size: 856 MB
  rows: 6001215 // 6 million

With Rest API + limit pushdown

  SELECT * FROM tpch10.lineitem_1 LIMIT 1; -- 1
  -- Input: 1 row (166B), Physical input time: 2.22s
  Execution time: ~4 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 10; -- 10
  -- Input: 10 rows (1.55kB), Physical input time: 2.85s
  Execution time: ~4 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 100; -- 100
  -- Input: 100 rows (15.28kB), Physical input time: 2.45s
  Execution time: ~4 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 1000; -- 1K
  -- Input: 1000 rows (152.78kB), Physical input time: 2.17s
  Execution time: ~4 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 2500; -- 2.5K
  -- Input: 2500 rows (382.77kB), Physical input time: 2.99s
  Execution time: ~5 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 5000; -- 5K
  -- Input: 5000 rows (765.49kB), Physical input time: 4.46s
  Execution time: ~6 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 7500; -- 7.5K
  -- Input: 7500 rows (1.12MB), Physical input time: 5.59s
  Execution time: ~7 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 10000; -- 10K
  -- Input: 10000 rows (1.49MB), Physical input time: 6.49s
  Execution time: ~8 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 100000; -- 100K
  -- Input: 100000 rows (14.95MB), Physical input time: 41.57s
  Execution time: ~40 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 250000; -- 250K
  -- Input: 250000 rows (37.38MB), Physical input time: 1.65m
  Execution time: ~1 minutes 37 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 500000; -- 500K
  -- Input: 500000 rows (74.76MB), Physical input time: 3.22m
  Execution time: ~3 minutes 14 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 1000000; -- 1 million
  -- Input: 1000000 rows (149.52MB), Physical input time: 6.42m
  Execution time: ~6 minutes 60 seconds

With Storage API without limit pushdown

  SELECT * FROM tpch10.lineitem_1 LIMIT 1; -- 1
  -- Input: 1792 rows (274.48kB), Physical input: 204.56kB, Physical input time: 1.49s
  Execution time: ~5 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 10; -- 10
  -- Input: 1792 rows (273.93kB), Physical input: 202.76kB, Physical input time: 997.29ms
  Execution time: ~5 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 100; -- 100
  -- Input: 1792 rows (274.82kB), Physical input: 204.91kB, Physical input time: 1.55s
  Execution time: ~5 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 1000; -- 1K
  -- Input: 3584 rows (548.75kB), Physical input: 407.66kB, Physical input time: 3.05s
  Execution time: ~5 seconds
  
  SELECT * FROM tpch10.lineitem_1 LIMIT 2500; -- 2.5K
  -- Input: 5376 rows (822.89kB), Physical input: 611.83kB, Physical input time: 5.01s
  Execution time: ~6 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 5000; -- 5K
  -- Input: 7168 rows (1.07MB), Physical input: 815.95kB, Physical input time: 6.37s
  Execution time: ~6 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 7500; -- 7.5K
  -- Input: 12544 rows (1.87MB), Physical input: 1.39MB, Physical input time: 10.97s
  Execution time: ~7 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 10000; -- 10K
  -- Input: 14336 rows (2.14MB), Physical input: 1.59MB, Physical input time: 13.24s
  Execution time: ~5 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 100000; -- 100K
  -- Input: 101709 rows (15.20MB), Physical input: 11.31MB, Physical input time: 23.33s
  Execution time: ~7 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 250000; -- 250K
  -- Input: 254029 rows (37.98MB), Physical input: 28.26MB, Physical input time: 28.88s
  Execution time: ~7 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 500000; -- 500K
  -- Input: 501325 rows (74.96MB), Physical input: 55.78MB, Physical input time: 38.63s
  Execution time: ~8 seconds

  SELECT * FROM tpch10.lineitem_1 LIMIT 1000000; -- 1 million
  -- Input: 1003085 rows (149.99MB), Physical input: 111.62MB, Physical input time: 1.05m
  Execution time: ~9 seconds

By observing this test, we are supporting LIMIT pushdown only for those queries that use REST API.

Release notes

## BigQuery
* Add support for LIMIT pushdown. ({issue}`23937`)

ebyhr · 2024-11-06T00:31:12Z

/test-with-secrets sha=2061c56273afc55ffabb8bb4e139e3260bf7488b

github-actions · 2024-11-06T00:32:46Z

The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/11694897950

krvikash · 2024-11-08T20:26:38Z

(rebased with master). Ready for review.

Praveen2112 · 2024-11-11T13:06:16Z

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQuerySplitSource.java

+        if (limit.isPresent()) {
+            // Storage API doesn't support limiting rows, but REST API supports LIMIT clause.
+            // So use REST API to pushdown limit.
+            return ImmutableList.of(BigQuerySplit.forViewStream(columns, filter, limit));
+        }


But what if the LIMIT size is too large or if the table is a wide one ?

Is it possible to estimate stream size beforehand and change the split mode based on that?

@Praveen2112 | @ebyhr ,

I have tested the limit with a managed table with Rest API + limit pushdown and with Storage API without limit pushdown.

The Storage API without limit pushdown generally performs better in most cases. However, the REST API with limit pushdown is only slightly faster by about 1–2 seconds when the physical data size is very small, around 1 MB.

Table

table size: 856 MB rows: 6001215 // 6 million

With Rest API + limit pushdown

SELECT * FROM tpch10.lineitem_1 LIMIT 1; -- 1 -- Input: 1 row (166B), Physical input time: 2.22s Execution time: ~4 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 10; -- 10 -- Input: 10 rows (1.55kB), Physical input time: 2.85s Execution time: ~4 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 100; -- 100 -- Input: 100 rows (15.28kB), Physical input time: 2.45s Execution time: ~4 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 1000; -- 1K -- Input: 1000 rows (152.78kB), Physical input time: 2.17s Execution time: ~4 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 2500; -- 2.5K -- Input: 2500 rows (382.77kB), Physical input time: 2.99s Execution time: ~5 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 5000; -- 5K -- Input: 5000 rows (765.49kB), Physical input time: 4.46s Execution time: ~6 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 7500; -- 7.5K -- Input: 7500 rows (1.12MB), Physical input time: 5.59s Execution time: ~7 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 10000; -- 10K -- Input: 10000 rows (1.49MB), Physical input time: 6.49s Execution time: ~8 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 100000; -- 100K -- Input: 100000 rows (14.95MB), Physical input time: 41.57s Execution time: ~40 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 250000; -- 250K -- Input: 250000 rows (37.38MB), Physical input time: 1.65m Execution time: ~1 minutes 37 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 500000; -- 500K -- Input: 500000 rows (74.76MB), Physical input time: 3.22m Execution time: ~3 minutes 14 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 1000000; -- 1 million -- Input: 1000000 rows (149.52MB), Physical input time: 6.42m Execution time: ~6 minutes 60 seconds

With Storage API without limit pushdown

SELECT * FROM tpch10.lineitem_1 LIMIT 1; -- 1 -- Input: 1792 rows (274.48kB), Physical input: 204.56kB, Physical input time: 1.49s Execution time: ~5 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 10; -- 10 -- Input: 1792 rows (273.93kB), Physical input: 202.76kB, Physical input time: 997.29ms Execution time: ~5 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 100; -- 100 -- Input: 1792 rows (274.82kB), Physical input: 204.91kB, Physical input time: 1.55s Execution time: ~5 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 1000; -- 1K -- Input: 3584 rows (548.75kB), Physical input: 407.66kB, Physical input time: 3.05s Execution time: ~5 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 2500; -- 2.5K -- Input: 5376 rows (822.89kB), Physical input: 611.83kB, Physical input time: 5.01s Execution time: ~6 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 5000; -- 5K -- Input: 7168 rows (1.07MB), Physical input: 815.95kB, Physical input time: 6.37s Execution time: ~6 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 7500; -- 7.5K -- Input: 12544 rows (1.87MB), Physical input: 1.39MB, Physical input time: 10.97s Execution time: ~7 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 10000; -- 10K -- Input: 14336 rows (2.14MB), Physical input: 1.59MB, Physical input time: 13.24s Execution time: ~5 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 100000; -- 100K -- Input: 101709 rows (15.20MB), Physical input: 11.31MB, Physical input time: 23.33s Execution time: ~7 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 250000; -- 250K -- Input: 254029 rows (37.98MB), Physical input: 28.26MB, Physical input time: 28.88s Execution time: ~7 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 500000; -- 500K -- Input: 501325 rows (74.96MB), Physical input: 55.78MB, Physical input time: 38.63s Execution time: ~8 seconds SELECT * FROM tpch10.lineitem_1 LIMIT 1000000; -- 1 million -- Input: 1003085 rows (149.99MB), Physical input: 111.62MB, Physical input time: 1.05m Execution time: ~9 seconds

For managed tables and for views/materialized views where skip_view_materialization is disabled,
The Storage API without limit pushdown usually gives better performance. The REST API with limit pushdown is only marginally faster (1-2 seconds) for very small data sizes, around 1 MB. So, I am choosing to skip the limit pushdown for these tables.

As for estimating stream size and adjusting split mode dynamically, we could implement something like shouldUseRestApiForLimit to decide between the REST API and Storage API. However, adding this would increase complexity without significant gains. Let me know if you think this is worth exploring further. CC: @ebyhr | @Praveen2112

private static final long DATA_THRESHOLD_TO_USE_REST_API_FOR_LIMIT = 1024 * 1024; // 1MB ... public static boolean shouldUseRestApiForLimit(TableInfo tableInfo, int projectedColumnsCount, long limit) { Schema schema = tableInfo.getDefinition().getSchema(); if (schema == null) { SchemaTableName schemaTableName = new SchemaTableName(tableInfo.getTableId().getDataset(), tableInfo.getTableId().getTable()); throw new TableNotFoundException(schemaTableName, format("Table '%s' has no schema", schemaTableName)); } long tableSize = tableInfo.getNumBytes(); long numRows = tableInfo.getNumRows().longValueExact(); int totalColumns = schema.getFields().size(); double columnFraction = (double) projectedColumnsCount / totalColumns; double estimatedSizePerRow = ((double) tableSize / numRows) * columnFraction; long expectedReadSize = (long) (estimatedSizePerRow * limit); return expectedReadSize < DATA_THRESHOLD_TO_USE_REST_API_FOR_LIMIT; }

krvikash · 2024-11-13T19:24:58Z

Limit pushdown will be supported for

external table
native query
view/materialized-view (with skip_view_materialization enabled)

krvikash · 2024-11-13T19:25:33Z

Hi @ebyhr, Could you please run this PR against secrets?

krvikash · 2024-11-13T19:32:45Z

(error-prone fix and rebased with master)

ebyhr · 2024-11-13T23:27:20Z

/test-with-secrets sha=788e9d5d3fa7e46fe3ec29cf462ce49c5fec6218

github-actions · 2024-11-13T23:29:02Z

The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/11827619150

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java

ebyhr · 2024-11-19T12:37:53Z

/test-with-secrets sha=cceef83d3ad45644c1a2958cbd59096f489f199f

github-actions · 2024-11-19T12:39:30Z

The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/11913214142

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQueryMetadata.java

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQueryQueryPageSource.java

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQuerySplitSource.java

krvikash · 2024-11-20T08:54:26Z

Thanks @pajaks | @findinpath for the review. AC.

Praveen2112

LGTM % changes.

Praveen2112 · 2024-11-21T06:04:16Z

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQueryClient.java

    }

-    public static String selectSql(TableId table, String formattedColumns, Optional<String> filter)
+    public static String selectSql(TableId table, String formattedColumns, Optional<String> filter, OptionalLong limit)
    {
        String tableName = fullTableName(table);
        String query = format("SELECT %s FROM `%s`", formattedColumns, tableName);


nit: Maybe as a follow-up - Can we use StringBuilder here ?

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQueryQueryPageSource.java

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQuerySplitSource.java

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java

Praveen2112 · 2024-11-21T06:35:24Z

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java

+        assertThat(query(session, "SELECT COUNT(*) FROM (SELECT * FROM %s LIMIT 3)".formatted(tableName)))
+                .matches("VALUES BIGINT '3'")
+                .isNotFullyPushedDown(aggregationOverTableScan);
+        assertThat(query(session, "SELECT COUNT(*) FROM (SELECT * FROM %s LIMIT 10)".formatted(tableName)))
+                .matches("VALUES BIGINT '5'")
+                .isNotFullyPushedDown(aggregationOverTableScan);


How do we ensure that LIMIT is pushed down here ? Can we add anyNot(LimitNode.class, ...) to ensure that Limit pushdown did happen here.

As discussed offline, Using tableScan to verify limit value.

Now verifying tableScan with limit along with anyNot(LimitNode.class, ...)

anyNot( LimitNode.class, node( AggregationNode.class, anyTree(node( AggregationNode.class, tableScan(table -> { BigQueryTableHandle actualTableHandle = (BigQueryTableHandle) table; return actualTableHandle.limit().equals(limit); }, TupleDomain.all(), ImmutableMap.of())))));

CC: @Praveen2112 ^^

krvikash · 2024-11-21T09:37:17Z

Thanks @Praveen2112 for the review. AC.

krvikash · 2024-11-21T10:32:05Z

(CI fix)

krvikash · 2024-11-22T11:30:35Z

(Pushed final set of changes for verifying plan)

krvikash · 2024-11-26T06:07:02Z

Hi @Praveen2112 Can this be merged if there are no comments?

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQueryUtil.java

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java

Limit pushdown will be supported only when query based approach is applied 1. external table 2. native query 3. view/materialized-view (with skip_view_materialization enabled)

krvikash · 2024-11-26T06:55:14Z

Thanks @Praveen2112. AC.

Praveen2112 · 2024-11-26T07:44:21Z

/test-with-secrets sha=57b217641b9a7798c234dfbb55ac836404caa99b

github-actions · 2024-11-26T07:46:03Z

The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/12026031079

krvikash · 2024-11-26T10:10:46Z

The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/12026031079

CI failure is unrelated to this PR.

cla-bot bot added the cla-signed label Nov 4, 2024

krvikash changed the title ~~Support limit pushdown in Bigquery connector~~ [WIP] Support limit pushdown in Bigquery connector Nov 4, 2024

github-actions bot added the bigquery BigQuery connector label Nov 4, 2024

krvikash force-pushed the bigquery-limit-pushdown branch 2 times, most recently from e3d5b41 to 2061c56 Compare November 5, 2024 17:19

krvikash changed the title ~~[WIP] Support limit pushdown in Bigquery connector~~ Support limit pushdown in Bigquery connector Nov 5, 2024

krvikash marked this pull request as ready for review November 5, 2024 17:20

krvikash requested review from ssheikin, ebyhr, Praveen2112, vlad-lyutenko, pajaks and marcinsbd November 5, 2024 17:20

krvikash marked this pull request as draft November 6, 2024 06:14

krvikash force-pushed the bigquery-limit-pushdown branch from 2061c56 to 23b37b3 Compare November 8, 2024 20:22

krvikash marked this pull request as ready for review November 8, 2024 20:25

Praveen2112 reviewed Nov 11, 2024

View reviewed changes

krvikash force-pushed the bigquery-limit-pushdown branch from 23b37b3 to 54851a7 Compare November 13, 2024 19:23

Simplify code in BigQuerySplitSource#getSplits

de361f2

krvikash force-pushed the bigquery-limit-pushdown branch from 54851a7 to 788e9d5 Compare November 13, 2024 19:32

ebyhr approved these changes Nov 19, 2024

View reviewed changes

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java Outdated Show resolved Hide resolved

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java Show resolved Hide resolved

krvikash force-pushed the bigquery-limit-pushdown branch from 788e9d5 to ca72aa6 Compare November 19, 2024 06:56

findinpath reviewed Nov 19, 2024

View reviewed changes

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java Show resolved Hide resolved

findinpath reviewed Nov 19, 2024

View reviewed changes

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQueryMetadata.java Outdated Show resolved Hide resolved

pajaks reviewed Nov 19, 2024

View reviewed changes

krvikash force-pushed the bigquery-limit-pushdown branch from cceef83 to 88e04b0 Compare November 20, 2024 08:54

pajaks approved these changes Nov 20, 2024

View reviewed changes

Praveen2112 approved these changes Nov 21, 2024

View reviewed changes

krvikash force-pushed the bigquery-limit-pushdown branch from 88e04b0 to 7a829b0 Compare November 21, 2024 09:33

krvikash force-pushed the bigquery-limit-pushdown branch from 7a829b0 to e643cbc Compare November 21, 2024 10:31

marcinsbd approved these changes Nov 21, 2024

View reviewed changes

SemionPar approved these changes Nov 21, 2024

View reviewed changes

krvikash force-pushed the bigquery-limit-pushdown branch from e643cbc to 4cab533 Compare November 22, 2024 11:27

Praveen2112 approved these changes Nov 26, 2024

View reviewed changes

plugin/trino-bigquery/src/main/java/io/trino/plugin/bigquery/BigQueryUtil.java Outdated Show resolved Hide resolved

plugin/trino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryConnectorTest.java Outdated Show resolved Hide resolved

Support Limit pushdown in Bigquery connector

57b2176

Limit pushdown will be supported only when query based approach is applied 1. external table 2. native query 3. view/materialized-view (with skip_view_materialization enabled)

krvikash force-pushed the bigquery-limit-pushdown branch from 4cab533 to 57b2176 Compare November 26, 2024 06:53

Praveen2112 merged commit 33cb3ad into trinodb:master Nov 26, 2024
15 of 16 checks passed

github-actions bot added this to the 466 milestone Nov 26, 2024

krvikash deleted the bigquery-limit-pushdown branch November 26, 2024 12:06

This was referenced Nov 27, 2024

Add Trino 466 release notes #24208

Merged

Add limit pushdown to BigQuery docs #24285

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support limit pushdown in Bigquery connector #24021

Support limit pushdown in Bigquery connector #24021

krvikash commented Nov 4, 2024 •

edited

Loading

ebyhr commented Nov 6, 2024

github-actions bot commented Nov 6, 2024

krvikash commented Nov 8, 2024

Praveen2112 Nov 11, 2024

ebyhr Nov 12, 2024

krvikash Nov 13, 2024

krvikash Nov 13, 2024

krvikash commented Nov 13, 2024

krvikash commented Nov 13, 2024

krvikash commented Nov 13, 2024

ebyhr commented Nov 13, 2024

github-actions bot commented Nov 13, 2024

ebyhr commented Nov 19, 2024

github-actions bot commented Nov 19, 2024

krvikash commented Nov 20, 2024

Praveen2112 left a comment

Praveen2112 Nov 21, 2024

Praveen2112 Nov 21, 2024

krvikash Nov 21, 2024

krvikash Nov 22, 2024

krvikash Nov 22, 2024

krvikash commented Nov 21, 2024

krvikash commented Nov 21, 2024

krvikash commented Nov 22, 2024

krvikash commented Nov 26, 2024

krvikash commented Nov 26, 2024

Praveen2112 commented Nov 26, 2024

github-actions bot commented Nov 26, 2024 •

edited

Loading

krvikash commented Nov 26, 2024

Support limit pushdown in Bigquery connector #24021

Support limit pushdown in Bigquery connector #24021

Conversation

krvikash commented Nov 4, 2024 • edited Loading

Description

Additional Context

Release notes

ebyhr commented Nov 6, 2024

github-actions bot commented Nov 6, 2024

krvikash commented Nov 8, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

krvikash commented Nov 13, 2024

krvikash commented Nov 13, 2024

krvikash commented Nov 13, 2024

ebyhr commented Nov 13, 2024

github-actions bot commented Nov 13, 2024

ebyhr commented Nov 19, 2024

github-actions bot commented Nov 19, 2024

krvikash commented Nov 20, 2024

Praveen2112 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

krvikash commented Nov 21, 2024

krvikash commented Nov 21, 2024

krvikash commented Nov 22, 2024

krvikash commented Nov 26, 2024

krvikash commented Nov 26, 2024

Praveen2112 commented Nov 26, 2024

github-actions bot commented Nov 26, 2024 • edited Loading

krvikash commented Nov 26, 2024

krvikash commented Nov 4, 2024 •

edited

Loading

github-actions bot commented Nov 26, 2024 •

edited

Loading