[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-02-01。"],[[["\u003cp\u003eData Catalog search queries can be simple, using a single predicate to match substrings in data asset names, types, column names, project IDs, or tag values, among other criteria.\u003c/p\u003e\n"],["\u003cp\u003eQualified predicates refine searches by using keys like \u003ccode\u003ename:\u003c/code\u003e, \u003ccode\u003edescription:\u003c/code\u003e, \u003ccode\u003etype=\u003c/code\u003e, and \u003ccode\u003elocation=\u003c/code\u003e to specify the metadata field being searched, and whether the search should match a substring (\u003ccode\u003e:\u003c/code\u003e), or exact match (\u003ccode\u003e=\u003c/code\u003e).\u003c/p\u003e\n"],["\u003cp\u003eSearch queries support a wide array of qualifiers including \u003ccode\u003ename\u003c/code\u003e, \u003ccode\u003edisplayname\u003c/code\u003e, \u003ccode\u003ecolumn\u003c/code\u003e, \u003ccode\u003edescription\u003c/code\u003e, \u003ccode\u003elabel\u003c/code\u003e, \u003ccode\u003etype\u003c/code\u003e, \u003ccode\u003eprojectid\u003c/code\u003e, \u003ccode\u003eparent\u003c/code\u003e, \u003ccode\u003eorgid\u003c/code\u003e, \u003ccode\u003esystem\u003c/code\u003e, \u003ccode\u003elocation\u003c/code\u003e, \u003ccode\u003etag\u003c/code\u003e, \u003ccode\u003ecreatetime\u003c/code\u003e, \u003ccode\u003eupdatetime\u003c/code\u003e, \u003ccode\u003epolicytag\u003c/code\u003e, \u003ccode\u003epolicytagid\u003c/code\u003e, \u003ccode\u003eterm\u003c/code\u003e, \u003ccode\u003efully_qualified_name\u003c/code\u003e, allowing for detailed searches.\u003c/p\u003e\n"],["\u003cp\u003eLogical operators such as \u003ccode\u003eAND\u003c/code\u003e, \u003ccode\u003eOR\u003c/code\u003e, and negation (\u003ccode\u003e-\u003c/code\u003e or \u003ccode\u003eNOT\u003c/code\u003e) can combine multiple predicates to create complex search queries, with \u003ccode\u003eAND\u003c/code\u003e being the default operator when no operator is specified.\u003c/p\u003e\n"],["\u003cp\u003eAn abbreviated syntax using \u003ccode\u003e|\u003c/code\u003e for \u003ccode\u003eOR\u003c/code\u003e and \u003ccode\u003e,\u003c/code\u003e for \u003ccode\u003eAND\u003c/code\u003e is available for certain qualified predicates (excluding \u003ccode\u003etag\u003c/code\u003e, \u003ccode\u003eterm\u003c/code\u003e, \u003ccode\u003epolicytag\u003c/code\u003e, \u003ccode\u003epolicytagid\u003c/code\u003e and \u003ccode\u003elabel\u003c/code\u003e), streamlining the construction of complex queries.\u003c/p\u003e\n"]]],[],null,["# Data Catalog search syntax\n\nThis document describes the syntax for Data Catalog search queries. Before you read this document, it is important that you understand the concepts of Data Catalog such as data entry, tags and tag templates, and other kinds of metadata. See [What is Data Catalog?](/data-catalog/docs/concepts/overview).\n\nTo launch a Data Catalog search query in the\nGoogle Cloud console, go to the Data Catalog **Search** page and\nselect **Data Catalog** as the search mode.\n\n[Go to Search](https://console.cloud.google.com/dataplex/search)\n\nSimple search\n-------------\n\nIn its simplest form, a Data Catalog search query comprises a single predicate. Such a\npredicate can match several pieces of metadata:\n\n- A substring of a name, display name, or description of a data asset\n- Exact type of a data asset\n- A substring of a column name (or [nested column](/bigquery/docs/nested-repeated) name) in the schema of a data asset\n- A substring of a project ID\n- The value of a public tag, the name of a public tag template, or a field name in a public tag template attached to a data entry.\n- (Preview) A string for an email address or name for a data steward\n- (Preview) A string from an overview description\n\nThe simple search does not support tag template fields of type `datetime`.\n\nFor example, the predicate `foo` matches the following entities:\n\n- Data asset with the `foo.bar` name\n- Data asset with the `Foo Bar` display name\n- Data asset with the description `This is the foo script.`\n- Data asset with the exact `foo` type\n- Column `foo_bar` in the schema of a data asset\n- Nested column `foo_bar` in the schema of a data asset\n- Project `prod-foo-bar`\n- Public tag template named `foo`, data entries tagged with the `foo` tag template, tag template display name of `foo`, tag template field name of `foo`, and tag field value of `foo` in a string, enum, or rich text.\n- (Preview) Data asset with a data steward called `foo`.\n- (Preview) Data asset with an overview containing the word `foo`.\n\nTo know more about the roles and permissions to view public and private tags, see [Roles to view public and private tags](/data-catalog/docs/concepts/iam#roles_to_view_public_and_private_tags).\n\nQualified predicates\n--------------------\n\nYou can qualify a predicate by prefixing it with a key that restricts the\nmatching to a specific piece of metadata.\n\nAn equal sign (`=`) restricts the search to an exact match.\n\nA colon (`:`) after the key matches the predicate to either a substring or token within\nthe value in search results.\n\nTokenization breaks the stream of text up into a series of tokens, with\neach token usually corresponding to a single word.\n\nFor example:\n\n- `name:foo` selects entities with names that contain the `foo` substring: `foo1` and `barfoo`.\n- `description:foo` selects entities with the `foo` token in the description: `bar and foo`.\n- `location=foo` matches all data assets in a specified location with `foo` as the location name.\n\n| **Note:** You can only search for an exact `type=foo`, `system=foo`, `location=foo`, or `orgid=number`. The corresponding predicate keys can't be followed by a colon.\n\nData Catalog supports the following qualifiers:\n\nLogical operators\n-----------------\n\nA query can be comprised of several\npredicates with logical operators. If you don't specify an operator, logical\n`AND` is implied. For example, `foo bar` returns entities that match both\npredicate `foo` and predicate `bar`.\n\nLogical AND and logical OR are supported, for example, `foo OR bar`.\n\nYou can negate a predicate with a `-` or `NOT` prefix. For example, `-name:foo` returns\nall entities with names that don't match the predicate `foo`.\n| Logical operators are not case-sensitive (for example, \"or\" and \"OR\" are acceptable).\n\n### Abbreviated syntax\n\nAn abbreviated search syntax is also available, using `|` for `OR` operators and\n`,` for `AND` operators.\n\nFor example, to search for entries inside one of many projects using the `OR`\noperator, you can use:\n\n`projectid:(pid1|pid2|pid3|pid4)`\n\nInstead of:\n\n`projectid:pid1 OR projectid:pid2 OR projectid:pid3 OR projectid:pid4`\n\nTo search for entries with matching column names:\n\n- AND: `column:(name1, name2, name3)`\n- OR: `column:(name1|name2|name3)`\n\nThis abbreviated syntax works for the [qualified\npredicates](#qualified_predicates) listed earlier, except for `tag`, `term`,\n`policytag`, `policytagid` and `label`."]]