Basic Search
Overview
To perform a basic search, you define search conditions by selecting the object properties, operators, and values that you want to search for.
For example, the following basic search finds all Data Collector pipelines modified after July 12, 2022:
Basic search is the default search mode and can be used for most search use cases. If you need to specify criteria that cannot be defined in basic search, such as defining complex conditions or changing the order of precedence for multiple conditions, then change to advanced mode to define an advanced search.
Multiple Conditions
A basic search can include one or more search conditions. When you include multiple conditions, you specify whether to join the conditions using AND or OR.
The AND operator takes precedence over OR. Control Hub first evaluates all conditions connected by an AND operator, and then evaluates each condition connected by an OR operator.
For example, let's say that you include the following conditions in a basic search:
Version is exactly 1 OR Version is exactly 2 AND Committed On is after or on
6/01/2022
- Finds pipelines with a latest version of 2 and that were committed on or after June 1, 2022.
- Finds pipelines with a latest version of 1 with no date restriction.
To define a different order of precedence, you must use advanced search and include parentheses in the search query.
Basic String Searches
For some search properties, such as Name, Description, or Commit Message, you enter a string as the value to search for.
Use the following guidelines when entering string values for a basic search:
- Case insensitive
- String values are case insensitive. For example, all of the following search
conditions find the Tutorial pipeline:
Name is exactly tutorial
Name is exactly TUTORIAL
Name is exactly tUtoRIaL
- Strings with spaces do not require quotation marks
- Do not enclose a string that includes spaces in quotation marks. For example,
the following search condition finds the HDFS to ADLS2
pipeline:
Name contains to ADLS2
- Asterisk wildcard
- Include the asterisk wildcard (*) in string values to perform a multiple
character wildcard search. For example, the following search condition finds the
LogsToKafka and LogsToKinesis
pipelines, but not the LogsToS3 pipeline:
Name begins with logs*k*
Labels, Tags, and Engine Labels
Label
property for pipelines and fragmentsTag
andEngine Label
properties for job instances and job templates
As you begin typing a value to search for, Control Hub displays a drop-down menu that lists values that match the entered characters. The values are case insensitive. You then select one or more values from the list.
For example, if you type OR
for the job instance Tag
property, the drop-down might display oracle
, store
,
and Oregon data center
because those are all valid tag values for your
job instances.
Nested Labels and Tags
Label
property for pipelines and fragmentsTag
property for job instances and job templates
You can search for a string value anywhere in a Label or Tag hierarchy, but cannot search for a complete hierarchy entry.
For example, if a pipeline has the label Test/ADLSGen2, you can search for the label Test or ADLSGen2. You cannot search for the complete label hierarchy, such as Test/ADLSGen2.
- PipelineA - Test/ADLSGen2/read
- PipelineB - Test/ADLSGen2/write
- PipelineC - Test/Elasticsearch
- PipelineD - Prod/write
The following basic search condition finds PipelineA, PipelineB, and PipelineC:
Label includes Test
The following advanced search condition finds PipelineB and PipelineD:
label==wri*
Pipeline and Fragment Versions
A pipeline or fragment search finds the latest pipeline or fragment version matching the search conditions.
For example, if version 6 is the latest version of the SocialFeedsDataflow pipeline, the following basic search condition finds version 6 of the pipeline:
name is exactly SocialFeedsDataflow
To find an older version, define a condition using the Version
property.
The Version property includes a string value. You can search for
draft versions, such as 1-DRAFT, or for published versions, such
as 3.
For example, the following basic search conditions find the older version 4 of the SocialFeedsDataflow pipeline:
name is exactly SocialFeedsDataflow AND Version is exactly 4
v
prefix so that the version number displays as
v1
or v3
. On other pages, the Version column does
not include the prefix so that the version number displays as 1
or
3
. In basic searches, you can include or exclude the prefix. For
example, you can search for either v1 or
1. In advanced searches, you must exclude the prefix. For
example, you must search for 1.When you define a condition using the Version
property, multiple
versions of a single pipeline or fragment can match all search conditions. In this case,
search still returns the latest version matching all search results.
For example, the LogstoOracle pipeline has the following version history:
If you search for version begins with 2
, four possible versions of the
LogstoOracle pipeline match the search condition - versions 2, 2.1, 2.2 and 2.1.1.
However, since search returns the latest pipeline version, only version 2.1.1 is
returned.
Basic Search | Advanced Search | Search Result |
---|---|---|
version begins with 2 |
version==2* |
version 2.1.1 |
version is exactly 1 OR version is exactly
3 |
version==1 or version==3 |
version 3 |
NA | version=in=(1,3,1.1,2.1) |
version 1.1 |
version is exactly 2.1 OR name begins with
L |
version==2.1 or name==L* |
version 2.1.1 |
Performing a Basic Search
Basic search is the default search mode and can be used for most search use cases.