Google BigQuery Adapter Limitations
Following are some of the limitations of the Google BigQuery adapter:
1. For clearing cache, the following two conditions must be met:
a. Rows can be removed from Google BigQuery tables after 90 minutes
b. The cache_status/cache_tracking tables should be pointed to a different datasource, such as PostgresSQL. It is recommended to choose the “Use a different data source” option, while defining the Cache status and Tracking tables.
2. In the caching configuration, while choosing the table for multi-table caching, the fields “Table Schema” and “Table Catalog” are not optional for Google BigQuery data source.
3. CREATE/DROP indexes for tables is not supported. You must uncheck the option "Drop indexes before load and create indexes after load" in the caching configuration before initiating caching.
4. In order to use the Select/Insert native cache loading functions, choose the “Enable Native Data Loading” in the Overrides panel and uncheck the “Use Streaming Inserts” option in the datasource configuration.
5. Native cache loading with Insert/Select is not supported for synthesized views.
6. The following datatypes are not supported by Google BigQuery. Tables with columns of these datatypes cannot be cached:
— BLOB
— CLOB
— BT_INT_LONG