INFORMATION_SCHEMA.SEARCH_INDEXES 뷰에는 데이터 세트에 있는 각 검색 색인에 대해 하나의 행이 포함되어 있습니다.
필수 권한
검색 색인 메타데이터를 보려면 색인이 있는 테이블에 대한 bigquery.tables.get 또는 bigquery.tables.list Identity and Access Management(IAM) 권한이 필요합니다. 다음과 같은 사전 정의된 IAM 역할에는 이러한 권한 중 하나 이상이 포함되어 있습니다.
선택사항: PROJECT_ID: Google Cloud 프로젝트의 ID입니다. 지정하지 않으면 기본 프로젝트가 사용됩니다.
DATASET_ID: 데이터 세트의 ID입니다. 자세한 내용은 데이터 세트 한정자를 참조하세요.
예시
-- Returns metadata for search indexes in a single dataset.SELECT*FROMmyDataset.INFORMATION_SCHEMA.SEARCH_INDEXES;
예
다음 예시는 my_project 프로젝트에 위치한 데이터 세트 my_dataset에 있는 테이블의 모든 활성 검색 색인을 보여줍니다. 여기에는 검색 색인의 이름, 검색 색인을 만드는 데 사용된 DDL 문, 적용 범위 비율, 텍스트 분석기가 포함됩니다. 색인이 생성된 기본 테이블이 10GB 미만이면 색인이 채워지지 않으며, 이 경우 coverage_percentage는 0입니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThe \u003ccode\u003eINFORMATION_SCHEMA.SEARCH_INDEXES\u003c/code\u003e view provides metadata for each search index within a dataset, with each row representing a unique index.\u003c/p\u003e\n"],["\u003cp\u003eAccessing search index metadata requires either the \u003ccode\u003ebigquery.tables.get\u003c/code\u003e or \u003ccode\u003ebigquery.tables.list\u003c/code\u003e IAM permission on the indexed table, which are included in several predefined IAM roles such as \u003ccode\u003eroles/bigquery.admin\u003c/code\u003e and \u003ccode\u003eroles/bigquery.dataViewer\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe view's schema includes details like \u003ccode\u003eindex_name\u003c/code\u003e, \u003ccode\u003eindex_status\u003c/code\u003e, \u003ccode\u003ecreation_time\u003c/code\u003e, \u003ccode\u003eDDL\u003c/code\u003e, \u003ccode\u003ecoverage_percentage\u003c/code\u003e, \u003ccode\u003eanalyzer\u003c/code\u003e and more, offering comprehensive information about each search index.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eindex_status\u003c/code\u003e field indicates the current state of the index, such as \u003ccode\u003eACTIVE\u003c/code\u003e, \u003ccode\u003ePENDING DISABLEMENT\u003c/code\u003e, \u003ccode\u003eTEMPORARILY DISABLED\u003c/code\u003e, or \u003ccode\u003ePERMANENTLY DISABLED\u003c/code\u003e, each having different implications on its usability and storage charges.\u003c/p\u003e\n"],["\u003cp\u003eQueries to this view must use a dataset qualifier, specifying the \u003ccode\u003ePROJECT_ID\u003c/code\u003e and \u003ccode\u003eDATASET_ID\u003c/code\u003e, and its scope is limited to the dataset's location, allowing users to retrieve metadata for search indexes within a specific dataset.\u003c/p\u003e\n"]]],[],null,["# SEARCH_INDEXES view\n===================\n\nThe `INFORMATION_SCHEMA.SEARCH_INDEXES` view contains one row for each search\nindex in a dataset.\n\nRequired permissions\n--------------------\n\nTo see [search index](/bigquery/docs/search-index) metadata, you need the\n`bigquery.tables.get` or `bigquery.tables.list` Identity and Access Management (IAM)\npermission on the table with the index. Each of the following predefined\nIAM roles includes at least one of these permissions:\n\n- `roles/bigquery.admin`\n- `roles/bigquery.dataEditor`\n- `roles/bigquery.dataOwner`\n- `roles/bigquery.dataViewer`\n- `roles/bigquery.metadataViewer`\n- `roles/bigquery.user`\n\nFor more information about BigQuery permissions, see\n[Access control with IAM](/bigquery/docs/access-control).\n\nSchema\n------\n\nWhen you query the `INFORMATION_SCHEMA.SEARCH_INDEXES` view, the query results contain one row for each search index in a dataset.\n\n\u003cbr /\u003e\n\nThe `INFORMATION_SCHEMA.SEARCH_INDEXES` view has the following schema:\n\nScope and syntax\n----------------\n\nQueries against this view must have a [dataset qualifier](/bigquery/docs/information-schema-intro#syntax). The\nfollowing table explains the region scope for this view:\n\nReplace the following:\n\n- Optional: \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of your Google Cloud project. If not specified, the default project is used.\n- \u003cvar translate=\"no\"\u003eDATASET_ID\u003c/var\u003e: the ID of your dataset. For more information, see [Dataset qualifier](/bigquery/docs/information-schema-intro#dataset_qualifier).\n\n\u003cbr /\u003e\n\n**Example** \n\n -- Returns metadata for search indexes in a single dataset.\n SELECT * FROM myDataset.INFORMATION_SCHEMA.SEARCH_INDEXES;\n\nExample\n-------\n\nThe following example shows all active search indexes on tables in the dataset\n`my_dataset`, located in the project `my_project`. It includes their names, the\nDDL statements used to create them, their coverage percentage, and their\ntext analyzer. If an indexed base table is\nless than 10GB, then its index is not populated, in which case\n`coverage_percentage` is 0. \n\n SELECT table_name, index_name, ddl, coverage_percentage, analyzer\n FROM my_project.my_dataset.INFORMATION_SCHEMA.SEARCH_INDEXES\n WHERE index_status = 'ACTIVE';\n\nThe results should look like the following: \n\n```\n+-------------+-------------+--------------------------------------------------------------------------------------+---------------------+----------------+\n| table_name | index_name | ddl | coverage_percentage | analyzer |\n+-------------+-------------+--------------------------------------------------------------------------------------+---------------------+----------------+\n| small_table | names_index | CREATE SEARCH INDEX `names_index` ON `my_project.my_dataset.small_table`(names) | 0 | NO_OP_ANALYZER |\n| large_table | logs_index | CREATE SEARCH INDEX `logs_index` ON `my_project.my_dataset.large_table`(ALL COLUMNS) | 100 | LOG_ANALYZER |\n+-------------+-------------+--------------------------------------------------------------------------------------+---------------------+----------------+\n```"]]
