Tune a model using your data

Preview

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

Note: To give feedback or request support for this feature, contact [e-mail].

This document shows you how to create a BigQuery ML remote model that references any version of the text-bison Vertex AI natural language foundation model and configures the model to perform supervised tuning. After you create the remote model, you use the ML.EVALUATE function to evaluate the model and confirm that the model's performance suits your use case. You can then use the model in conjunction with the ML.GENERATE_TEXT function to analyze text in a BigQuery table.

Required permissions

• To create a connection, you need membership in the following Identity and Access Management (IAM) role:

  • roles/bigquery.connectionAdmin

• To grant permissions to the connection's service account, you need the following permission:

  • resourcemanager.projects.setIamPolicy

• To create the model using BigQuery ML, you need the following IAM permissions:

  • bigquery.jobs.create
  • bigquery.models.create
  • bigquery.models.getData
  • bigquery.models.updateData
  • bigquery.models.updateMetadata

• To run inference, you need the following permissions:

  • bigquery.tables.getData on the table
  • bigquery.models.getData on the model
  • bigquery.jobs.create

Before you begin

1. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

   Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

   Go to project selector

2. Make sure that billing is enabled for your Google Cloud project.

3. Enable the BigQuery, BigQuery Connection,Vertex AI, and Compute Engine APIs.

   Enable the APIs

Create a connection

Create a Cloud resource connection and get the connection's service account.

Select one of the following options:

Console

1. Go to the BigQuery page.

   Go to BigQuery

2. To create a connection, click Add, and then click Connections to external data sources.

3. In the Connection type list, select Vertex AI remote models, remote functions and BigLake (Cloud Resource).

4. In the Connection ID field, enter a name for your connection.

5. Click Create connection.

6. Click Go to connection.

7. In the Connection info pane, copy the service account ID for use in a later step.

bq

1. In a command-line environment, create a connection:

   bq mk --connection --location=REGION --project_id=PROJECT_ID \
       --connection_type=CLOUD_RESOURCE CONNECTION_ID
   

   The --project_id parameter overrides the default project.

   Replace the following:

   • REGION: your connection region
   • PROJECT_ID: your Google Cloud project ID
   • CONNECTION_ID: an ID for your connection

   When you create a connection resource, BigQuery creates a unique system service account and associates it with the connection.

   Troubleshooting: If you get the following connection error, update the Google Cloud SDK:

   Flags parsing error: flag --connection_type=CLOUD_RESOURCE: value should be one of...
   

2. Retrieve and copy the service account ID for use in a later step:

   bq show --connection PROJECT_ID.REGION.CONNECTION_ID
   

   The output is similar to the following:

   name                          properties
   1234.REGION.CONNECTION_ID     {"serviceAccountId": "[e-mail]"}
   

Terraform

Append the following section into your main.tf file.

 ## This creates a cloud resource connection.
 ## Note: The cloud resource nested object has only one output only field - serviceAccountId.
 resource "google_bigquery_connection" "connection" {
    connection_id = "CONNECTION_ID"
    project = "PROJECT_ID"
    location = "REGION"
    cloud_resource {}
}        

Replace the following:

• CONNECTION_ID: an ID for your connection
• PROJECT_ID: your Google Cloud project ID
• REGION: your connection region

Give the connection's service account access

Give your service account permission to access Vertex AI. Failure to give permission results in an error. Select one of the following options:

Console

1. Go to the IAM & Admin page.

   Go to IAM & Admin

2. Click Grant Access.

3. For New principals, enter the service account ID that you copied earlier.

4. Click Select a role.

5. In Filter, type Vertex AI Service Agent and then select that role.

6. Click Save.

gcloud

Use the gcloud projects add-iam-policy-binding command:

gcloud projects add-iam-policy-binding 'PROJECT_NUMBER' --member='serviceAccount:MEMBER' --role='roles/aiplatform.serviceAgent' --condition=None

Replace the following:

• PROJECT_NUMBER: your project number.
• MEMBER: the service account ID that you copied earlier.

The service account associated with your connection is an instance of the BigQuery Connection Delegation Service Agent, so it is OK to assign a service agent role to it.

Give the Compute Engine default service account access

When you enable the Compute Engine API, the Compute Engine default service account is automatically granted the Editor role on the project, unless you have disabled this behavior for your project. If that's the case, then you must re-grant the Editor role to the Compute Engine default service account access so that it has sufficient permissions to create and tune a remote model.

Console

1. Go to the IAM & Admin page.

   Go to IAM & Admin

2. Click Grant Access.

3. For New principals, enter the service account ID, which is [e-mail].

4. Click Select a role.

5. In Select a role, choose Basic and then select Editor.

6. Click Save.

gcloud

Use the gcloud projects add-iam-policy-binding command:

gcloud projects add-iam-policy-binding 'PROJECT_NUMBER' --member='serviceAccount:MEMBER' --role='roles/editor' --condition=None

Replace the following:

• PROJECT_NUMBER: your project number.
• MEMBER: the service account ID, which is [e-mail].

Create a model with supervised tuning

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. In the query editor, run the following query to create a remote model:

   CREATE OR REPLACE MODEL
   `PROJECT_ID.DATASET_ID.MODEL_NAME`
   REMOTE WITH CONNECTION `PROJECT_ID.REGION.CONNECTION_ID`
   OPTIONS (
     ENDPOINT = 'ENDPOINT',
     MAX_ITERATIONS = MAX_ITERATIONS,
     EARLY_STOP = EARLY_STOP,
     LEARNING_RATE_MULTIPLIER = LEARNING_RATE_MULTIPLIER,
     ACCELERATOR_TYPE = 'ACCELERATOR_TYPE',
     DATA_SPLIT_METHOD = 'DATA_SPLIT_METHOD',
     DATA_SPLIT_EVAL_FRACTION = DATA_SPLIT_EVAL_FRACTION,
     DATA_SPLIT_COL = 'DATA_SPLIT_COL',
     EVALUATION_TASK = 'EVALUATION_TASK',
     PROMPT_COL = 'INPUT_PROMPT_COL',
     INPUT_LABEL_COLS = INPUT_LABEL_COLS)
   AS SELECT PROMPT_COLUMN, LABEL_COLUMN
   FROM `TABLE_PROJECT_ID.TABLE_DATASET.TABLE_NAME`;
   

   Replace the following:

   • PROJECT_ID: the project ID of the project in which to create the model.
   • DATASET_ID: the ID of the dataset to contain the model. This dataset must be in a supported pipeline job and model upload region.
   • MODEL_NAME: the name of the model.
   • REGION: the region used by the connection.
   • CONNECTION_ID: the ID of your BigQuery connection. This connection must be in the same location as the dataset that you are using.

     When you view the connection details in the Google Cloud console, this is the value in the last section of the fully qualified connection ID that is shown in Connection ID—for example, projects/myproject/locations/connection_location/connections/myconnection.

   • ENDPOINT: a STRING value that specifies the name of the text LLM to use, which in this case must be any version of the text-bison model.
   • MAX_ITERATIONS: an INT64 value that specifies the number of steps to run for supervised tuning. The MAX_ITERATIONS value must be between 1 and 2400. Typically, 100 steps takes about an hour to complete. The default value is 300.

     The MAX_ITERATIONS value in combination with the ACCELERATOR_TYPE value affects the batch size used in model training. For more guidance on choosing the number of training steps, see Recommended configurations.

     For more information, see MAX_ITERATIONS.

   • EARLY_STOP: a BOOL value that determines whether to stop supervised tuning before completing all of the tuning steps. When set to TRUE, it stops supervised tuning if model performance, as measured by the accuracy of predicted tokens, doesn't improve enough between evaluation runs. When set to FALSE, supervised tuning continues until all the tuning steps are complete. The default value is FALSE.
   • LEARNING_RATE_MULTIPLIER: a FLOAT64 A multiplier to apply to the recommended learning rate. The default value is 1.0.
   • ACCELERATOR_TYPE: a STRING value that specifies the type of accelerator to use for supervised tuning. The valid options are the following:
     • GPU: uses A100 80 GB GPUs for supervised tuning.
     • TPU: uses 64 cores of the TPU v3 pod for supervised tuning. If you choose this option, the following is true:
       • You must run your query in the europe-west4 region. For information about changing query options such as the location, see Run an interactive query.
       • Your supervised tuning computations occur in the europe-west4 region, because that's where TPU resources are located.

     The default value is GPU. Whichever option you use, make sure you have enough quota.

   • DATA_SPLIT_METHOD: a STRING value that specifies the method used to split input data into training and evaluation sets. The valid options are the following:
     • AUTO_SPLIT: BigQuery ML automatically splits the data. The way in which the data is split varies depending on the number of rows in the input table. This is the default value.
     • RANDOM: data is randomized before being split into sets. To customize the data split, you can use this option with the DATA_SPLIT_EVAL_FRACTION option.
     • CUSTOM: data is split using the column provided in the DATA_SPLIT_COL option. The DATA_SPLIT_COL value must be the name of a column of type BOOL. Rows with a value of TRUE or NULL are used as evaluation data, and rows with a value of FALSE are used as training data.
     • SEQ: split data using the column provided in the DATA_SPLIT_COL option. The DATA_SPLIT_COL value must be the name of a column of one of the following types:
       • NUMERIC
       • BIGNUMERIC
       • STRING
       • TIMESTAMP

       The data is sorted smallest to largest based on the specified column.

       The first n rows are used as evaluation data, where n is the value specified for DATA_SPLIT_EVAL_FRACTION. The remaining rows are used as training data.

     • NO_SPLIT: no data split; all input data is used as training data.

     For more information about these data split options, see DATA_SPLIT_METHOD.

   • DATA_SPLIT_EVAL_FRACTION: a FLOAT64 value that specifies the fraction of the data to use as evaluation data when performing supervised tuning. Must be a value in the range [0, 1.0]. The default value is 0.2.

     Use this option when you specify RANDOM or SEQ as the value for the DATA_SPLIT_METHOD option. To customize the data split, you can use the DATA_SPLIT_METHOD option with the DATA_SPLIT_EVAL_FRACTION option.

   • DATA_SPLIT_COL: a STRING value that specifies the name of the column to use to sort input data into the training or evaluation set. Use when you are specifying CUSTOM or SEQ as the value for the DATA_SPLIT_METHOD option.
   • EVALUATION_TASK: a STRING value that specifies the type of task that you want to tune the model to perform. The valid options are:
     • TEXT_GENERATION
     • CLASSIFICATION
     • SUMMARIZATION
     • QUESTION_ANSWERING
     • UNSPECIFIED

     The default value is UNSPECIFIED.

   • INPUT_PROMPT_COL: a STRING value that contains the name of the prompt column in the training data table to use when performing supervised tuning. The default value is prompt.
   • INPUT_LABEL_COLS: an ARRAY<<STRING> value that contains the name of the label column in the training data table to use in supervised tuning. You can only specify one element in the array. The default value is an empty array. This causes label to be the default value of the LABEL_COLUMN argument.
   • PROMPT_COLUMN: the column in the training data table that contains the prompt for evaluating the content in the LABEL_COLUMN column. This column must be of STRING type or be cast to STRING. If you specify a value for the INPUT_PROMPT_COL option, you must specify the same value for PROMPT_COLUMN. Otherwise this value must be prompt. If your table does not have a prompt column, use an alias to specify an existing table column. For example, AS SELECT hint AS prompt, label FROM mydataset.mytable.
   • LABEL_COLUMN: the column in the training data table that contains the examples to train the model with. This column must be of STRING type or be cast to STRING. If you specify a value for the INPUT_LABEL_COLS option, you must specify the same value for LABEL_COLUMN. Otherwise this value must be label. If your table does not have a label column, use an alias to specify an existing table column. For example, AS SELECT prompt, feature AS label FROM mydataset.mytable.
   • TABLE_PROJECT_ID: the project ID of the project that contains the training data table.
   • TABLE_DATASET: the name of the dataset that contains the training data table.
   • TABLE_NAME: the name of the table that contains the data to use to train the model.

Evaluate the tuned model

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. In the query editor, run the following query to evaluate the tuned model:

   SELECT
   *
   FROM
   ML.EVALUATE(
     MODEL `PROJECT_ID.DATASET_ID.MODEL_NAME`,
     TABLE `TABLE_PROJECT_ID.TABLE_DATASET.TABLE_NAME`,
     STRUCT('TASK_TYPE' AS task_type, TOKENS AS max_output_tokens,
       TEMPERATURE AS temperature, TOP_K AS top_k,
       TOP_P AS top_p));
   

   Replace the following:

   • PROJECT_ID: the project ID of the project that contains the model.
   • DATASET_ID: the ID of the dataset that contains the model.
   • MODEL_NAME: the name of the model.
   • TABLE_PROJECT_ID: the project ID of the project that contains the evaluation data table.
   • TABLE_DATASET: the name of the dataset that contains the evaluation data table.
   • TABLE_NAME: the name of the table that contains the evaluation data.

     The table must have a column whose name matches the prompt column name that is provided during model training. You can provide this value by using the prompt_col option during model training. If prompt_col is unspecified, the column named prompt in the training data is used. An error is returned if there is no column named prompt.

     The table must have a column whose name matches the label column name that is provided during model training. You can provide this value by using the input_label_cols option during model training. If input_label_cols is unspecified, the column named label in the training data is used. An error is returned if there is no column named label.

   • TASK_TYPE: a STRING value that specifies the type of task that you want to evaluate the model for. The valid options are:
     • TEXT_GENERATION
     • CLASSIFICATION
     • SUMMARIZATION
     • QUESTION_ANSWERING
     • UNSPECIFIED
   • TOKENS: an INT64 value that sets the maximum number of tokens that can be generated in the response. This value must be in the range [1,1024]. Specify a lower value for shorter responses and a higher value for longer responses. The default is 128.
   • TEMPERATURE: a FLOAT64 value in the range [0.0,1.0] that controls the degree of randomness in token selection. The default is 0.

     Lower values for temperature are good for prompts that require a more deterministic and less open-ended or creative response, while higher values for temperature can lead to more diverse or creative results. A value of 0 for temperature is deterministic, meaning that the highest probability response is always selected.

   • TOP_K: an INT64 value in the range [1,40] that determines the initial pool of tokens the model considers for selection. Specify a lower value for less random responses and a higher value for more random responses. The default is 40.
   • TOP_P: a FLOAT64 value in the range [0.0,1.0] helps determine which tokens from the pool determined by TOP_K are selected. Specify a lower value for less random responses and a higher value for more random responses. The default is 0.95.

Generate text

Generate text with the ML.GENERATE_TEXT function:

Prompt column

Generate text by using a table column to provide the prompt.

SELECT *
FROM ML.GENERATE_TEXT(
  MODEL `PROJECT_ID.DATASET_ID.MODEL_NAME`,
  TABLE PROJECT_ID.DATASET_ID.TABLE_NAME,
  STRUCT(TOKENS AS max_output_tokens, TEMPERATURE AS temperature,
  TOP_K AS top_k, TOP_P AS top_p, FLATTEN_JSON AS flatten_json_output,
  STOP_SEQUENCES AS stop_sequences)
);

Replace the following:

• PROJECT_ID: your project ID.
• DATASET_ID: the ID of the dataset that contains the model.
• MODEL_NAME: the name of the model.
• TABLE_NAME: the name of the table that contains the prompt. This table must have a column whose name matches the name of the feature column in the tuned LLM. The feature column name in the LLM can be set by using the PROMPT_COL option when creating the model. Otherwise, the feature column name in the LLM is prompt by default, or you can use an alias to use a differently named column.
• TOKENS: an INT64 value that sets the maximum number of tokens that can be generated in the response. This value must be in the range [1,1024]. Specify a lower value for shorter responses and a higher value for longer responses. The default is 128.
• TEMPERATURE: a FLOAT64 value in the range [0.0,1.0] that controls the degree of randomness in token selection. The default is 0.

  Lower values for temperature are good for prompts that require a more deterministic and less open-ended or creative response, while higher values for temperature can lead to more diverse or creative results. A value of 0 for temperature is deterministic, meaning that the highest probability response is always selected.

• TOP_K: an INT64 value in the range [1,40] that determines the initial pool of tokens the model considers for selection. Specify a lower value for less random responses and a higher value for more random responses. The default is 40.
• TOP_P: a FLOAT64 value in the range [0.0,1.0] helps determine which tokens from the pool determined by TOP_K are selected. Specify a lower value for less random responses and a higher value for more random responses. The default is 0.95.
• FLATTEN_JSON: a BOOL value that determines whether to return the generated text and the safety attributes in separate columns. The default is FALSE.
• STOP_SEQUENCES: an ARRAY<STRING> value that removes the specified strings if they are included in responses from the model. Strings are matched exactly, including capitalization. The default is an empty array.

The following example shows a request with these characteristics:

• Uses the prompt column of the prompts table for the prompt.
• Returns a short and moderately probable response.
• Returns the generated text and the safety attributes in separate columns.

SELECT *
FROM
  ML.GENERATE_TEXT(
    MODEL `mydataset.llm_model`,
    TABLE mydataset.prompts,
    STRUCT(
      0.4 AS temperature, 100 AS max_output_tokens, 0.5 AS top_p,
      40 AS top_k, TRUE AS flatten_json_output));

Prompt query

Generate text by using a query to provide the prompt.

SELECT *
FROM ML.GENERATE_TEXT(
  MODEL `PROJECT_ID.DATASET_ID.MODEL_NAME`,
  (PROMPT_QUERY),
  STRUCT(TOKENS AS max_output_tokens, TEMPERATURE AS temperature,
  TOP_K AS top_k, TOP_P AS top_p, FLATTEN_JSON AS flatten_json_output,
  STOP_SEQUENCES AS stop_sequences)
);

Replace the following:

• PROJECT_ID: your project ID.
• DATASET_ID: the ID of the dataset that contains the model.
• MODEL_NAME: the name of the model.
• PROMPT_QUERY: a query that provides the prompt data.
• TOKENS: an INT64 value that sets the maximum number of tokens that can be generated in the response. This value must be in the range [1,1024]. Specify a lower value for shorter responses and a higher value for longer responses. The default is 128.
• TEMPERATURE: a FLOAT64 value in the range [0.0,1.0] that controls the degree of randomness in token selection. The default is 0.

  Lower values for temperature are good for prompts that require a more deterministic and less open-ended or creative response, while higher values for temperature can lead to more diverse or creative results. A value of 0 for temperature is deterministic, meaning that the highest probability response is always selected.

• TOP_K: an INT64 value in the range [1,40] that determines the initial pool of tokens the model considers for selection. Specify a lower value for less random responses and a higher value for more random responses. The default is 40.
• TOP_P: a FLOAT64 value in the range [0.0,1.0] helps determine which tokens from the pool determined by TOP_K are selected. Specify a lower value for less random responses and a higher value for more random responses. The default is 0.95.
• FLATTEN_JSON: a BOOL value that determines whether to return the generated text and the safety attributes in separate columns. The default is FALSE.
• STOP_SEQUENCES: an ARRAY<STRING> value that removes the specified strings if they are included in responses from the model. Strings are matched exactly, including capitalization. The default is an empty array.

Example 1

The following example shows a request with these characteristics:

• Prompts for a summary of the text in the body column of the articles table.
• Returns a moderately long and more probable response.
• Returns the generated text and the safety attributes in separate columns.

SELECT *
FROM
  ML.GENERATE_TEXT(
    MODEL `mydataset.llm_model`,
    (
      SELECT CONCAT('Summarize this text', body) AS prompt
      FROM mydataset.articles
    ),
    STRUCT(
      0.2 AS temperature, 650 AS max_output_tokens, 0.2 AS top_p,
      15 AS top_k, TRUE AS flatten_json_output));

Example 2

The following example shows a request with these characteristics:

• Uses a query to create the prompt data by concatenating strings that provide prompt prefixes with table columns.
• Returns a short and moderately probable response.
• Doesn't return the generated text and the safety attributes in separate columns.

SELECT *
FROM
  ML.GENERATE_TEXT(
    MODEL `mydataset.llm_tuned_model`,
    (
      SELECT CONCAT(question, 'Text:', description, 'Category') AS prompt
      FROM mydataset.input_table
    ),
    STRUCT(
      0.4 AS temperature, 100 AS max_output_tokens, 0.5 AS top_p,
      30 AS top_k, FALSE AS flatten_json_output));