[[["易于理解","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-08-08。"],[[["\u003cp\u003eDataplex Catalog search queries can be simple, consisting of a single predicate that matches substrings in resource names, types, descriptions, column names, project IDs, or overview descriptions.\u003c/p\u003e\n"],["\u003cp\u003eQualified predicates, using prefixes like \u003ccode\u003e=\u003c/code\u003e, and \u003ccode\u003e:\u003c/code\u003e, can be used to refine searches by restricting matches to exact values or substrings within specific metadata fields like names, descriptions, and locations.\u003c/p\u003e\n"],["\u003cp\u003eSearches can include logical operators \u003ccode\u003eAND\u003c/code\u003e, \u003ccode\u003eOR\u003c/code\u003e, and negation (\u003ccode\u003e-\u003c/code\u003e or \u003ccode\u003eNOT\u003c/code\u003e) to combine or exclude predicates, allowing for more complex search criteria, and use an abbreviated syntax with \u003ccode\u003e|\u003c/code\u003e for \u003ccode\u003eOR\u003c/code\u003e and \u003ccode\u003e,\u003c/code\u003e for \u003ccode\u003eAND\u003c/code\u003e operators.\u003c/p\u003e\n"],["\u003cp\u003eAspect searches allow filtering entries based on their attached aspects and field values, supporting various operators like \u003ccode\u003e=\u003c/code\u003e, \u003ccode\u003e:\u003c/code\u003e, \u003ccode\u003e<\u003c/code\u003e, \u003ccode\u003e>\u003c/code\u003e, and datetime comparisons for different data types.\u003c/p\u003e\n"],["\u003cp\u003eVarious qualifiers are available for searching, such as \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\u003ecreatetime\u003c/code\u003e, \u003ccode\u003eupdatetime\u003c/code\u003e, and \u003ccode\u003efully_qualified_name\u003c/code\u003e, each tailored to match specific resource attributes.\u003c/p\u003e\n"]]],[],null,["# Search syntax for Dataplex Universal Catalog\n\nThis document describes the syntax for Dataplex Universal Catalog search queries. Before\nyou read this document, it is important that you understand concepts for metadata\nmanagement in Dataplex Universal Catalog, such as entries, aspects, aspect types,\nentry groups, and entry types. For more information, see\n[About metadata management in Dataplex Universal Catalog](/dataplex/docs/catalog-overview).\n\nTo launch a Dataplex Universal Catalog search query in the\nGoogle Cloud console, go to the Dataplex Universal Catalog **Search** page, and\nthen select **Dataplex Universal Catalog** as the search mode.\n\n\n[Go to Search](https://console.cloud.google.com/dataplex/dp-search)\n\n\u003cbr /\u003e\n\nFor more information, see\n[Search for resources in Dataplex Universal Catalog](/dataplex/docs/search-assets).\n\nSimple search\n-------------\n\nIn its simplest form, a Dataplex Universal Catalog search query consists\nof a single predicate. Such a predicate can match several pieces of metadata:\n\n- A substring of a name, display name, or description of a resource\n- A substring of the type of a resource\n- A substring of a column name (or [nested column](/bigquery/docs/nested-repeated) name) in the schema of a resource\n- A substring of a project ID\n- A string from an overview description\n\nFor example, the predicate `foo` matches the following resources:\n\n- Resource with the name `foo.bar`\n- Resource with the display name `Foo Bar`\n- Resource with the description `This is the foo script`\n- Resource with the exact type `foo`\n- Column `foo_bar` in the schema of a resource\n- Nested column `foo_bar` in the schema of a resource\n- Project `prod-foo-bar`\n- Resource with an overview containing the word `foo`\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\n- An equal sign (`=`) restricts the search to an exact match.\n- A colon (`:`) after the key matches the predicate to either a substring or a token within the value in the search results.\n\nTokenization splits the stream of text into a series of tokens, with each\ntoken usually corresponding to a single word.\n\nFor example:\n\n- `name:foo` selects resources with names that contain the `foo` substring, like `foo1` and `barfoo`.\n- `description:foo` selects resources with the `foo` token in the description, like `bar` and `foo`.\n- `location=foo` matches resources in a specified location with `foo` as the location name.\n\nThe predicate keys `type`, `system`, `location`, and `orgid` support only the\nexact match (`=`) qualifier, not the substring qualifier (`:`). For example,\n`type=foo` or `orgid=number`.\n\nDataplex Universal Catalog supports the following qualifiers:\n\nAspect search\n-------------\n\nTo search for entries based on their attached aspects, use the following query\nsyntax.\n| **Note:** The substring match tries to match against a limited number of aspects. If you can't find the entry by using a fragment of the path, then use the full path to narrow the search and increase recall.\n\nLogical operators\n-----------------\n\nA query can consist of several predicates with logical operators. If you don't\nspecify an operator, logical `AND` is implied. For example, `foo bar` returns\nresources that match both predicate `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 `-` (hyphen) or `NOT` prefix. For example,\n`-name:foo` returns resources with names that don't match the predicate `foo`.\n\nLogical operators aren't case-sensitive. For example, both `or` and `OR` are\nacceptable.\n\n### Abbreviated syntax\n\nAn abbreviated search syntax is also available, using `|` (vertical bar) for\n`OR` operators and `,` (comma) for `AND` operators.\n\nFor example, to search for entries inside one of many projects using the `OR`\noperator, you can use the following abbreviated syntax: \n\n projectid:(id1|id2|id3|id4)\n\nThe same search without using abbreviated syntax looks like the following: \n\n projectid:id1 OR projectid:id2 OR projectid:id3 OR projectid:id4\n\nTo search for entries with matching column names, use the following:\n\n- **AND** : `column:(name1, name2, name3)`\n- **OR** : `column:(name1|name2|name3)`\n\nThis abbreviated syntax works for the\n[qualified predicates](#qualified-predicates) except for `label`.\n\nWhat's next\n-----------\n\n- Learn how to [search for resources](/dataplex/docs/search-assets) in Dataplex Universal Catalog\n- Learn more [about metadata management in Dataplex Universal Catalog](/dataplex/docs/catalog-overview).\n- Learn how to [enrich entries with metadata by using aspects](/dataplex/docs/enrich-entries-metadata).\n- Learn how to [manage entries and ingest custom sources](/dataplex/docs/ingest-custom-sources)."]]
