Reference documentation and code samples for the Cloud Logging V2 API class Google::Cloud::Logging::V2::BigQueryOptions.
Options that change functionality of a sink exporting data to BigQuery.
Inherits
Object
Extended By
Google::Protobuf::MessageExts::ClassMethods
Includes
Google::Protobuf::MessageExts
Methods
#use_partitioned_tables
defuse_partitioned_tables()->::Boolean
Returns
(::Boolean) — Optional. Whether to use BigQuery's partition
tables. By
default, Cloud Logging creates dated tables based on the log entries'
timestamps, e.g. syslog_20170523. With partitioned tables the date suffix
is no longer present and special query
syntax
has to be used instead. In both cases, tables are sharded based on UTC
timezone.
#use_partitioned_tables=
defuse_partitioned_tables=(value)->::Boolean
Parameter
value (::Boolean) — Optional. Whether to use BigQuery's partition
tables. By
default, Cloud Logging creates dated tables based on the log entries'
timestamps, e.g. syslog_20170523. With partitioned tables the date suffix
is no longer present and special query
syntax
has to be used instead. In both cases, tables are sharded based on UTC
timezone.
Returns
(::Boolean) — Optional. Whether to use BigQuery's partition
tables. By
default, Cloud Logging creates dated tables based on the log entries'
timestamps, e.g. syslog_20170523. With partitioned tables the date suffix
is no longer present and special query
syntax
has to be used instead. In both cases, tables are sharded based on UTC
timezone.
(::Boolean) — Output only. True if new timestamp column based partitioning is in use,
false if legacy ingestion-time partitioning is in use.
All new sinks will have this field set true and will use timestamp column
based partitioning. If use_partitioned_tables is false, this value has no
meaning and will be false. Legacy sinks using partitioned tables will have
this field set to false.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Cloud Logging V2 API - Class Google::Cloud::Logging::V2::BigQueryOptions (v1.3.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.3.0 (latest)](/ruby/docs/reference/google-cloud-logging-v2/latest/Google-Cloud-Logging-V2-BigQueryOptions)\n- [1.2.1](/ruby/docs/reference/google-cloud-logging-v2/1.2.1/Google-Cloud-Logging-V2-BigQueryOptions)\n- [1.1.0](/ruby/docs/reference/google-cloud-logging-v2/1.1.0/Google-Cloud-Logging-V2-BigQueryOptions)\n- [1.0.1](/ruby/docs/reference/google-cloud-logging-v2/1.0.1/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.13.0](/ruby/docs/reference/google-cloud-logging-v2/0.13.0/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.12.2](/ruby/docs/reference/google-cloud-logging-v2/0.12.2/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.11.0](/ruby/docs/reference/google-cloud-logging-v2/0.11.0/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.10.1](/ruby/docs/reference/google-cloud-logging-v2/0.10.1/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.9.0](/ruby/docs/reference/google-cloud-logging-v2/0.9.0/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.8.1](/ruby/docs/reference/google-cloud-logging-v2/0.8.1/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.7.0](/ruby/docs/reference/google-cloud-logging-v2/0.7.0/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.6.0](/ruby/docs/reference/google-cloud-logging-v2/0.6.0/Google-Cloud-Logging-V2-BigQueryOptions)\n- [0.5.6](/ruby/docs/reference/google-cloud-logging-v2/0.5.6/Google-Cloud-Logging-V2-BigQueryOptions) \nReference documentation and code samples for the Cloud Logging V2 API class Google::Cloud::Logging::V2::BigQueryOptions.\n\nOptions that change functionality of a sink exporting data to BigQuery. \n\nInherits\n--------\n\n- Object \n\nExtended By\n-----------\n\n- Google::Protobuf::MessageExts::ClassMethods \n\nIncludes\n--------\n\n- Google::Protobuf::MessageExts\n\nMethods\n-------\n\n### #use_partitioned_tables\n\n def use_partitioned_tables() -\u003e ::Boolean\n\n**Returns**\n\n- (::Boolean) --- Optional. Whether to use [BigQuery's partition\n tables](https://cloud.google.com/bigquery/docs/partitioned-tables). By default, Cloud Logging creates dated tables based on the log entries' timestamps, e.g. syslog_20170523. With partitioned tables the date suffix is no longer present and [special query\n syntax](https://cloud.google.com/bigquery/docs/querying-partitioned-tables) has to be used instead. In both cases, tables are sharded based on UTC timezone.\n\n### #use_partitioned_tables=\n\n def use_partitioned_tables=(value) -\u003e ::Boolean\n\n**Parameter**\n\n- **value** (::Boolean) --- Optional. Whether to use [BigQuery's partition\n tables](https://cloud.google.com/bigquery/docs/partitioned-tables). By default, Cloud Logging creates dated tables based on the log entries' timestamps, e.g. syslog_20170523. With partitioned tables the date suffix is no longer present and [special query\nsyntax](https://cloud.google.com/bigquery/docs/querying-partitioned-tables) has to be used instead. In both cases, tables are sharded based on UTC timezone. \n**Returns**\n\n- (::Boolean) --- Optional. Whether to use [BigQuery's partition\n tables](https://cloud.google.com/bigquery/docs/partitioned-tables). By default, Cloud Logging creates dated tables based on the log entries' timestamps, e.g. syslog_20170523. With partitioned tables the date suffix is no longer present and [special query\n syntax](https://cloud.google.com/bigquery/docs/querying-partitioned-tables) has to be used instead. In both cases, tables are sharded based on UTC timezone.\n\n### #uses_timestamp_column_partitioning\n\n def uses_timestamp_column_partitioning() -\u003e ::Boolean\n\n**Returns**\n\n- (::Boolean) --- Output only. True if new timestamp column based partitioning is in use, false if legacy ingestion-time partitioning is in use.\n\n All new sinks will have this field set true and will use timestamp column\n based partitioning. If use_partitioned_tables is false, this value has no\n meaning and will be false. Legacy sinks using partitioned tables will have\n this field set to false."]]