Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Mengelola model
Dokumen ini menunjukkan cara mengelola model BigQuery ML, termasuk menyalin model dan mengganti nama model.
Peran yang diperlukan
Untuk mendapatkan izin yang diperlukan untuk membaca dan membuat model BigQuery, minta administrator untuk memberi Anda peran IAM BigQuery Data Editor (roles/bigquery.dataEditor) di project.
Untuk mengetahui informasi selengkapnya tentang cara memberikan peran, lihat Mengelola akses ke project, folder, dan organisasi.
Peran bawaan ini berisi
izin yang diperlukan untuk membaca dan membuat model BigQuery. Untuk melihat izin yang benar-benar diperlukan, luaskan bagian Izin yang diperlukan:
Izin yang diperlukan
Izin berikut diperlukan untuk membaca dan membuat model BigQuery:
Untuk membaca informasi dari model:
bigquery.models.getData
Anda tidak dapat mengubah nama model yang ada. Jika Anda perlu mengubah nama model, ikuti langkah-langkah untuk menyalin model. Saat Anda menentukan tujuan dalam operasi penyalinan, gunakan nama model baru.
Salin model
Anda dapat menyalin satu atau beberapa model dari set data sumber ke set data tujuan dengan:
Menggunakan Google Cloud console.
Menggunakan perintah bq cp alat command line bq.
Memanggil metode API jobs.insert secara langsung dan mengonfigurasi tugas penyalinan atau dengan menggunakan library klien.
Batasan dalam menyalin model
Tugas penyalinan model tunduk pada batasan berikut:
Saat Anda menyalin model, nama model tujuan harus mematuhi konvensi penamaan yang sama dengan saat Anda membuat model.
Salinan model tunduk pada batas BigQuery pada tugas penyalinan.
Konsol Google Cloud tidak mendukung penyalinan model.
Menyalin beberapa model sumber dalam satu perintah tidak didukung.
Saat Anda menyalin model menggunakan CLI, flag --destination_kms_key tidak didukung.
Konsol Google Cloud tidak mendukung penyalinan model.
bq
Berikan perintah bq cp. Flag opsional:
-f atau --force menimpa model yang ada di set data tujuan dan tidak meminta konfirmasi Anda.
-n atau --no_clobber menampilkan pesan error berikut jika model ada dalam set data tujuan: '[PROJECT_ID]:[DATASET].[MODEL]'
already exists, skipping.
Jika -n tidak ditentukan, perilaku default-nya adalah meminta Anda untuk memilih apakah akan mengganti model tujuan.
Jika set data sumber atau tujuan berada di project selain project default
Anda, tambahkan project ID ke nama set data dalam format berikut:
PROJECT_ID:DATASET.
Berikan
flag --location dan tetapkan nilai ke
lokasi Anda.
LOCATION:
nama lokasi Anda. Flag --location bersifat opsional. Misalnya, jika menggunakan BigQuery di region Tokyo, Anda dapat menetapkan nilai flag ke asia-northeast1. Anda dapat
menetapkan nilai default untuk lokasi menggunakan
file.bigqueryrc.
Untuk mengetahui daftar lengkap lokasi, lihat
Lokasi BigQuery.
PROJECT_ID: project ID Anda.
DATASET: nama set data sumber atau tujuan.
SOURCE_MODEL: model yang Anda salin.
DESTINATION_MODEL: nama model dalam set data tujuan.
Contoh:
Masukkan perintah berikut untuk menyalin mydataset.mymodel ke
mydataset2.
Kedua set data berada di project default Anda dan dibuat di lokasi multi-region US.
Masukkan perintah berikut untuk menyalin mydataset.mymodel dan untuk menimpa model tujuan dengan nama yang sama. Set data sumber ada di project default Anda. Set data tujuan ada di myotherproject. Pintasan -f digunakan
untuk menimpa model tujuan tanpa perintah.
mydataset dan myotherdataset dibuat di lokasi multi-region US.
Masukkan perintah berikut untuk menyalin mydataset.mymodel dan menampilkan error jika set data tujuan berisi model dengan nama yang sama. Set data sumber berada di project default Anda. Set data tujuan ada di
myotherproject. Pintasan -n digunakan untuk mencegah menimpa model dengan nama yang sama.
Kedua
set data dibuat di lokasi multi-region US.
Masukkan perintah berikut untuk menyalin mydataset.mymodel menjadi mydataset2 dan mengganti nama model mymodel2. Kedua set data ada dalam project default Anda.
Kedua set data dibuat di region asia-northeast1.
Untuk menyalin model menggunakan API, panggil metode
bigquery.jobs.insert
dan konfigurasikan tugas copy. Tentukan lokasi Anda di
properti location di bagian jobReference
di resource lowongan.
Anda harus menentukan nilai berikut dalam konfigurasi tugas:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis document explains how to manage BigQuery ML models, focusing on copying and renaming models, as directly renaming existing models is not supported.\u003c/p\u003e\n"],["\u003cp\u003eTo read and create BigQuery models, users need the \u003ccode\u003ebigquery.models.getData\u003c/code\u003e and \u003ccode\u003ebigquery.models.create\u003c/code\u003e permissions, respectively, which are included in the \u003ccode\u003eroles/bigquery.dataEditor\u003c/code\u003e IAM role.\u003c/p\u003e\n"],["\u003cp\u003eModels can be copied to a destination dataset using the Google Cloud command-line tool (\u003ccode\u003ebq cp\u003c/code\u003e), API (\u003ccode\u003ejobs.insert\u003c/code\u003e), or client libraries, but not the Google Cloud console, and they must adhere to specific naming conventions.\u003c/p\u003e\n"],["\u003cp\u003eCopying models with the command-line tool (\u003ccode\u003ebq cp\u003c/code\u003e) supports options to overwrite (\u003ccode\u003e-f\u003c/code\u003e) or prevent overwriting (\u003ccode\u003e-n\u003c/code\u003e) existing models at the destination, but the \u003ccode\u003e--destination_kms_key\u003c/code\u003e flag is unsupported.\u003c/p\u003e\n"],["\u003cp\u003eWhile model renaming is not directly supported, it can be achieved by copying a model to a new destination and assigning it the desired name during the copy operation.\u003c/p\u003e\n"]]],[],null,["# Manage models\n=============\n\nThis document shows you how to manage BigQuery ML models, including\ncopying models and renaming models.\n\nRequired roles\n--------------\n\n\nTo get the permissions that\nyou need to read and create BigQuery models,\n\nask your administrator to grant you the\n\n\n[BigQuery Data Editor](/iam/docs/roles-permissions/bigquery#bigquery.dataEditor) (`roles/bigquery.dataEditor`)\nIAM role on the project.\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nThis predefined role contains\n\nthe permissions required to read and create BigQuery models. To see the exact permissions that are\nrequired, expand the **Required permissions** section:\n\n\n#### Required permissions\n\nThe following permissions are required to read and create BigQuery models:\n\n- To read information from models: ` ``bigquery.models.getData`\n- To create models: ` ``bigquery.models.create`\n\n\nYou might also be able to get\nthese permissions\nwith [custom roles](/iam/docs/creating-custom-roles) or\nother [predefined roles](/iam/docs/roles-overview#predefined).\n\nRename models\n-------------\n\nYou cannot change the name of an existing model. If you need to\nchange the model's name, follow the steps to [copy the model](#copy-model). When\nyou specify the destination in the copy operation, use the new model name.\n\nCopy models\n-----------\n\nYou can copy one or more models from a source dataset to a destination dataset\nby:\n\n- Using the Google Cloud console.\n- Using the bq command-line tool's `bq cp` command.\n- Calling the [jobs.insert](/bigquery/docs/reference/rest/v2/jobs/insert) API method directly and configuring a [copy job](/bigquery/docs/reference/rest/v2/Job#JobConfigurationTableCopy) or by using the client libraries.\n\n### Limitations on copying models\n\nModel copy jobs are subject to the following limitations:\n\n- When you copy a model, the name of the destination model must adhere to the same naming conventions as when you [create a model](/bigquery/docs/reference/standard-sql/bigqueryml-syntax-create#model_name).\n- Model copies are subject to BigQuery [limits](/bigquery/quotas#copy_jobs) on copy jobs.\n- Copying a model is not supported by the Google Cloud console.\n- Copying multiple source models in a single command is not supported.\n- When you copy a model by using the CLI, the `--destination_kms_key` flag is not supported.\n\n### Copy a model\n\nYou can copy a model by:\n\n- Using the command-line tool's `bq cp` command\n- Calling the [`jobs.insert`](/bigquery/docs/reference/rest/v2/jobs/insert) API method and configuring a [copy job](/bigquery/docs/reference/rest/v2/Job#JobConfigurationTableCopy) or by using the client libraries\n\nTo copy a model: \n\n### Console\n\nThe Google Cloud console does not support copying models.\n\n### bq\n\nIssue the `bq cp` command. Optional flags:\n\n- `-f` or `--force` overwrites an existing model in the destination dataset and doesn't prompt you for confirmation.\n- `-n` or `--no_clobber` returns the following error message if the model\n exists in the destination dataset: `'[PROJECT_ID]:[DATASET].[MODEL]'\n already exists, skipping`.\n\n If `-n` is not specified, the default behavior is to prompt you to choose\n whether to replace the destination model.\n\n| **Note:** The `--destination_kms_key` flag is not supported when you copy a model.\n\nIf the source or destination dataset is in a project other than your default\nproject, add the project ID to the dataset names in the following format:\n\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e`:`\u003cvar translate=\"no\"\u003eDATASET\u003c/var\u003e.\n\nSupply the\n`--location` flag and set the value to your\n[location](/bigquery/docs/locations). \n\n```bash\nbq --location=LOCATION cp -f -n PROJECT_ID:DATASET.SOURCE_MODEL PROJECT_ID:DATASET.DESTINATION_MODEL\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the name of your location. The `--location` flag is optional. For example, if you are using BigQuery in the Tokyo region, you can set the flag's value to `asia-northeast1`. You can set a default value for the location using the [.bigqueryrc file](/bigquery/docs/bq-command-line-tool#setting_default_values_for_command-line_flags). For a full list of locations, see [BigQuery locations](/bigquery/docs/locations).\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your project ID.\n- \u003cvar translate=\"no\"\u003eDATASET\u003c/var\u003e: the name of the source or destination dataset.\n- \u003cvar translate=\"no\"\u003eSOURCE_MODEL\u003c/var\u003e: the model you're copying.\n- \u003cvar translate=\"no\"\u003eDESTINATION_MODEL\u003c/var\u003e: the name of the model in the destination dataset.\n\nExamples:\n\nEnter the following command to copy `mydataset.mymodel` to\n`mydataset2`.\n\nBoth datasets are in your default project and were\ncreated in the `US` multi-region location. \n\n```\nbq --location=US cp mydataset.mymodel mydataset2.mymodel\n```\n\nEnter the following command to copy `mydataset.mymodel` and to overwrite a\ndestination model with the same name. The source dataset is in your default\nproject. The destination dataset is in `myotherproject`. The `-f` shortcut is\nused to overwrite the destination model without a prompt.\n`mydataset` and\n`myotherdataset` were created in the `US` multi-region\nlocation. \n\n```\nbq --location=US cp -f mydataset.mymodel myotherproject:myotherdataset.mymodel\n```\n\nEnter the following command to copy `mydataset.mymodel` and to return an error\nif the destination dataset contains a model with the same name. The source\ndataset is in your default project. The destination dataset is in\n`myotherproject`. The `-n` shortcut is used to prevent overwriting a model with\nthe same name.\nBoth\ndatasets were created in the `US` multi-region location. \n\n```\nbq --location=US cp -n mydataset.mymodel myotherproject:myotherdataset.mymodel\n```\n\nEnter the following command to copy `mydataset.mymodel` to `mydataset2` and\nto rename the model `mymodel2`. Both datasets are in your default project.\nBoth datasets were created in the `asia-northeast1` region. \n\n```\nbq --location=asia-northeast1 cp mydataset.mymodel mydataset2.mymodel2\n```\n\n### API\n\nTo copy a model by using the API, call the\n[`bigquery.jobs.insert`](/bigquery/docs/reference/rest/v2/jobs/insert)\nmethod and configure a `copy` job. Specify your location in the\n`location` property in the `jobReference` section of the\n[job resource](/bigquery/docs/reference/rest/v2/jobs).\n\nYou must specify the following values in your job configuration: \n\n```\n\"copy\": {\n \"sourceTable\": { // Required\n \"projectId\": string, // Required\n \"datasetId\": string, // Required\n \"tableId\": string // Required\n },\n \"destinationTable\": { // Required\n \"projectId\": string, // Required\n \"datasetId\": string, // Required\n \"tableId\": string // Required\n },\n \"createDisposition\": string, // Optional\n \"writeDisposition\": string, // Optional\n },\n```\n\nWhere:\n\n- `sourceTable`: provides information about the model to be copied.\n- `destinationTable`: provides information about the new model.\n- [createDisposition](/bigquery/docs/reference/rest/v2/Job#JobConfigurationTableCopy.FIELDS.create_disposition): specifies whether to create the model if it doesn't exist.\n- [writeDisposition](/bigquery/docs/reference/rest/v2/Job#JobConfigurationTableCopy.FIELDS.write_disposition): specifies whether to overwrite an existing model.\n\nEncrypt models\n--------------\n\nFor more information about using a customer-managed encryption key (CMEK) to\nencrypt a model, see\n[Use CMEK to protect BigQuery ML models](/bigquery/docs/customer-managed-encryption#cmek-bqml).\n\nWhat's next\n-----------\n\n- For an overview of BigQuery ML, see [Introduction to BigQuery ML](/bigquery/docs/bqml-introduction).\n- To get started using BigQuery ML, see [Create machine learning models in BigQuery ML](/bigquery/docs/create-machine-learning-model).\n- To learn more about working with models, see:\n - [Get model metadata](/bigquery/docs/getting-model-metadata)\n - [List models](/bigquery/docs/listing-models)\n - [Update model metadata](/bigquery/docs/updating-model-metadata)\n - [Delete models](/bigquery/docs/deleting-models)\n - [Manage models with Vertex AI](/bigquery/docs/managing-models-vertex)"]]
