Note: Since other database objects may depend upon this table, drop. This guarantees that after the component succeeds the table matches the schema defined in this component, however any existing data in an existing table will be lost. Replace This drops any existing table of the same name, and then creates a new table. If the schema of the existing table does not match the schema defined in this component, no attempt is made to fix or correct it, which could lead to errors later in the job if you did not expect an existing table to exist, or to have a different schema to the one defined in this component. This will generate an error if a table with the same name already exists, but will never destroy existing data.Ĭreate if not exists: This will only create a new table if a table of the same name does not already exist. REPEATED: Field can accept multiple values Create/Replace Select Create: The default option, creates a new table. REQUIRED: Field does not accept null values ![]() Define Nested Metadata When the Define Nested Metadata checkbox is ticked inside the 'Table Metadata' property, a tree-structure can be defined for metadata. Timestamp: this type is a timestamp left unformatted (exists as Unix/Epoch Time). See the GCP documentation.ĭateTime: a formatted timestamp containing both date and time that is easily readable by the user. Time: a formatted time object without date. Numeric: this data type is suitable for data of an exact numeric value, allowing 38 digits of precision and 9 decimal digits of scale.īoolean: this type is suitable for data that is either 'true' or 'false'.ĭate: a formatted date object without time. Integer: this type is suitable for whole-number types (no decimals).įloat: this type is suitable for numeric types, with or without decimals. String: this type can hold any kind of data, subject to a maximum size. Table Metadata Column Name The name of the new column Data Type For more information on available BigQuery data types please refer to the GCP documentation. New Table Name Text Select an existing table to load data into. Dataset Text Enter the name of the Google Cloud Platform Dataset that the table belongs to. Project Text Enter the name of the Google Cloud Platform Project that the table belongs to. This is automatically determined from the table name when the Table Name property is first set. Properties Property Setting Description Name Text A human-readable name for the component. To learn more, read Access link-shared files using resource keys. These links can be amended by creating a new shared link in Google Drive. Shared links using the type=anyone or type=domain options (created in 2017 or earlier) may no longer function. To do this, use the following command (completed with your own information in the ) in the Google BigQuery console: gcloud beta compute instances set-scopes -service-account -scopes Due to limitations of how Google BigQuery communicates with Google Drive, it may be necessary to grant additional API scope - even beyond Allow full access to all Cloud APIs. Read Google Query Authentication Guide for details. ![]() It is essential that your GCP credentials have the Google Drive API enabled. sampled), an error may then occur when the referenced data cannot be accessed. However, when the table itself is used (e.g. ![]() Should a sheet be specified that Matillion ETL does not have proper access to, this component may still successfully run, as it is merely referencing the data in a table. Publicly viewable Google sheets can be accessed and used by Matillion ETL, regardless of credentials. That is to say that the GCP credentials used in Matillion ETL must be from an account that has the right to at least view the data. Your Matillion ETL instance must have access to this Google Drive data. New to Google Drive? Read Introduction to Google Drive API. Create a table that references data stored in Google Drive.
0 Comments
Leave a Reply. |