Struct google_jobs3::api::JobQuery
source · pub struct JobQuery {Show 13 fields
pub commute_filter: Option<CommuteFilter>,
pub company_display_names: Option<Vec<String>>,
pub company_names: Option<Vec<String>>,
pub compensation_filter: Option<CompensationFilter>,
pub custom_attribute_filter: Option<String>,
pub disable_spell_check: Option<bool>,
pub employment_types: Option<Vec<String>>,
pub job_categories: Option<Vec<String>>,
pub language_codes: Option<Vec<String>>,
pub location_filters: Option<Vec<LocationFilter>>,
pub publish_time_range: Option<TimestampRange>,
pub query: Option<String>,
pub query_language_code: Option<String>,
}Expand description
Input only. The query required to perform a search query.
This type is not used in any activity, and only used as part of another schema.
Fields§
§commute_filter: Option<CommuteFilter>Optional. Allows filtering jobs by commute time with different travel methods (for example, driving or public transit). Note: This only works with COMMUTE MODE. When specified, [JobQuery.location_filters] is ignored. Currently we don’t support sorting by commute time.
company_display_names: Option<Vec<String>>Optional. This filter specifies the company Company.display_name of the jobs to search against. The company name must match the value exactly. Alternatively, the value being searched for can be wrapped in different match operators. SUBSTRING_MATCH([value]) The company name must contain a case insensitive substring match of the value. Using this function may increase latency. Sample Value: SUBSTRING_MATCH(google) MULTI_WORD_TOKEN_MATCH([value]) The value will be treated as a multi word token and the company name must contain a case insensitive match of the value. Using this function may increase latency. Sample Value: MULTI_WORD_TOKEN_MATCH(google) If a value isn’t specified, jobs within the search results are associated with any company. If multiple values are specified, jobs within the search results may be associated with any of the specified companies. At most 20 company display name filters are allowed.
company_names: Option<Vec<String>>Optional. This filter specifies the company entities to search against. If a value isn’t specified, jobs are searched for against all companies. If multiple values are specified, jobs are searched against the companies specified. The format is “projects/{project_id}/companies/{company_id}”, for example, “projects/api-test-project/companies/foo”. At most 20 company filters are allowed.
compensation_filter: Option<CompensationFilter>Optional. This search filter is applied only to Job.compensation_info. For example, if the filter is specified as “Hourly job with per-hour compensation > $15”, only jobs meeting these criteria are searched. If a filter isn’t defined, all open jobs are searched.
custom_attribute_filter: Option<String>Optional. This filter specifies a structured syntax to match against the Job.custom_attributes marked as filterable. The syntax for this expression is a subset of SQL syntax. Supported operators are: =, !=, <, <=, >, and >= where the left of the operator is a custom field key and the right of the operator is a number or a quoted string. You must escape backslash (\) and quote (") characters. Supported functions are LOWER([field_name]) to perform a case insensitive match and EMPTY([field_name]) to filter on the existence of a key. Boolean expressions (AND/OR/NOT) are supported up to 3 levels of nesting (for example, “((A AND B AND C) OR NOT D) AND E”), a maximum of 100 comparisons or functions are allowed in the expression. The expression must be < 10000 bytes in length. Sample Query: (LOWER(driving_license)="class \"a\"" OR EMPTY(driving_license)) AND driving_years > 10
disable_spell_check: Option<bool>Optional. This flag controls the spell-check feature. If false, the service attempts to correct a misspelled query, for example, “enginee” is corrected to “engineer”. Defaults to false: a spell check is performed.
employment_types: Option<Vec<String>>Optional. The employment type filter specifies the employment type of jobs to search against, such as EmploymentType.FULL_TIME. If a value is not specified, jobs in the search results includes any employment type. If multiple values are specified, jobs in the search results include any of the specified employment types.
job_categories: Option<Vec<String>>Optional. The category filter specifies the categories of jobs to search against. See Category for more information. If a value is not specified, jobs from any category are searched against. If multiple values are specified, jobs from any of the specified categories are searched against.
language_codes: Option<Vec<String>>Optional. This filter specifies the locale of jobs to search against, for example, “en-US”. If a value isn’t specified, the search results can contain jobs in any locale. Language codes should be in BCP-47 format, such as “en-US” or “sr-Latn”. For more information, see Tags for Identifying Languages. At most 10 language code filters are allowed.
location_filters: Option<Vec<LocationFilter>>Optional. The location filter specifies geo-regions containing the jobs to search against. See LocationFilter for more information. If a location value isn’t specified, jobs fitting the other search criteria are retrieved regardless of where they’re located. If multiple values are specified, jobs are retrieved from any of the specified locations. If different values are specified for the LocationFilter.distance_in_miles parameter, the maximum provided distance is used for all locations. At most 5 location filters are allowed.
publish_time_range: Option<TimestampRange>Optional. Jobs published within a range specified by this filter are searched against.
query: Option<String>Optional. The query string that matches against the job title, description, and location fields. The maximum number of allowed characters is 255.
query_language_code: Option<String>The language code of query. For example, “en-US”. This field helps to better interpret the query. If a value isn’t specified, the query language code is automatically detected, which may not be accurate. Language code should be in BCP-47 format, such as “en-US” or “sr-Latn”. For more information, see Tags for Identifying Languages.