Skip to content

Commit c72d738

Browse files
Google APIscopybara-github
authored andcommitted
feat: A new enum RelevanceThreshold is added
feat: A new field `relevance_threshold` is added to message `.google.cloud.talent.v4.SearchJobsRequest` docs: multiple fixes for links in documentation PiperOrigin-RevId: 711534942
1 parent 651af4b commit c72d738

3 files changed

Lines changed: 47 additions & 13 deletions

File tree

google/cloud/talent/v4/filters.proto

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -261,7 +261,8 @@ message LocationFilter {
261261
// [PostingRegion.TELECOMMUTE][google.cloud.talent.v4.PostingRegion.TELECOMMUTE]
262262
// and have additional [Job.addresses][google.cloud.talent.v4.Job.addresses]
263263
// may still be matched based on other location filters using
264-
// [address][google.cloud.talent.v4.LocationFilter.address] or [latlng][].
264+
// [address][google.cloud.talent.v4.LocationFilter.address] or
265+
// [lat_lng][google.cloud.talent.v4.LocationFilter.lat_lng].
265266
//
266267
// This filter can be used by itself to search exclusively for telecommuting
267268
// jobs, or it can be combined with another location

google/cloud/talent/v4/job.proto

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -172,13 +172,16 @@ message Job {
172172
// search experience.
173173
//
174174
// Jobs with multiple addresses must have their addresses with the same
175-
// [LocationType][] to allow location filtering to work properly. (For
176-
// example, a Job with addresses "1600 Amphitheatre Parkway, Mountain View,
177-
// CA, USA" and "London, UK" may not have location filters applied correctly
178-
// at search time since the first is a [LocationType.STREET_ADDRESS][] and the
179-
// second is a [LocationType.LOCALITY][].) If a job needs to have multiple
180-
// addresses, it is suggested to split it into multiple jobs with same
181-
// LocationTypes.
175+
// [LocationType][google.cloud.talent.v4.Location.LocationType] to allow
176+
// location filtering to work properly. (For example, a Job with addresses
177+
// "1600 Amphitheatre Parkway, Mountain View, CA, USA" and "London, UK" may
178+
// not have location filters applied correctly at search time since the first
179+
// is a
180+
// [LocationType.STREET_ADDRESS][google.cloud.talent.v4.Location.LocationType.STREET_ADDRESS]
181+
// and the second is a
182+
// [LocationType.LOCALITY][google.cloud.talent.v4.Location.LocationType.LOCALITY].)
183+
// If a job needs to have multiple addresses, it is suggested to split it into
184+
// multiple jobs with same LocationTypes.
182185
//
183186
// The maximum number of allowed characters is 500.
184187
repeated string addresses = 6;
@@ -339,10 +342,11 @@ message Job {
339342
// [posting_publish_time][google.cloud.talent.v4.Job.posting_publish_time]
340343
// must be set before
341344
// [posting_expire_time][google.cloud.talent.v4.Job.posting_expire_time]. The
342-
// purpose of this feature is to allow other objects, such as [Application][],
343-
// to refer a job that didn't exist in the system prior to becoming expired.
344-
// If you want to modify a job that was expired on creation, delete it and
345-
// create a new one.
345+
// purpose of this feature is to allow other objects, such as
346+
// [ApplicationInfo][google.cloud.talent.v4.Job.ApplicationInfo], to refer a
347+
// job that didn't exist in the system prior to becoming expired. If you want
348+
// to modify a job that was expired on creation, delete it and create a new
349+
// one.
346350
//
347351
// If this value isn't provided at the time of job creation or is invalid,
348352
// the job posting expires after 30 days from the job's creation time. For

google/cloud/talent/v4/job_service.proto

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -448,6 +448,27 @@ message SearchJobsRequest {
448448
KEYWORD_MATCH_TITLE_ONLY = 3;
449449
}
450450

451+
// The relevance threshold of the search results. The higher relevance
452+
// threshold is, the higher relevant results are shown and the less number of
453+
// results are returned.
454+
enum RelevanceThreshold {
455+
// Default value. In this case, server behavior defaults to Google defined
456+
// threshold.
457+
RELEVANCE_THRESHOLD_UNSPECIFIED = 0;
458+
459+
// Lowest relevance threshold.
460+
LOWEST = 1;
461+
462+
// Low relevance threshold.
463+
LOW = 2;
464+
465+
// Medium relevance threshold.
466+
MEDIUM = 3;
467+
468+
// High relevance threshold.
469+
HIGH = 4;
470+
}
471+
451472
// Custom ranking information for
452473
// [SearchJobsRequest][google.cloud.talent.v4.SearchJobsRequest].
453474
message CustomRankingInfo {
@@ -811,6 +832,14 @@ message SearchJobsRequest {
811832
// [KeywordMatchMode.KEYWORD_MATCH_ALL][google.cloud.talent.v4.SearchJobsRequest.KeywordMatchMode.KEYWORD_MATCH_ALL]
812833
// if no value is specified.
813834
KeywordMatchMode keyword_match_mode = 18;
835+
836+
// Optional. The relevance threshold of the search results.
837+
//
838+
// Default to Google defined threshold, leveraging a balance of
839+
// precision and recall to deliver both highly accurate results and
840+
// comprehensive coverage of relevant information.
841+
RelevanceThreshold relevance_threshold = 19
842+
[(google.api.field_behavior) = OPTIONAL];
814843
}
815844

816845
// Response for SearchJob method.
@@ -939,7 +968,7 @@ message BatchUpdateJobsRequest {
939968
//
940969
// If [update_mask][google.cloud.talent.v4.BatchUpdateJobsRequest.update_mask]
941970
// is provided, The [Job][google.cloud.talent.v4.Job] inside
942-
// [JobResult][JobOperationResult.JobResult]
971+
// [JobResult][google.cloud.talent.v4.JobResult]
943972
// will only contains fields that is updated, plus the Id of the Job.
944973
// Otherwise, [Job][google.cloud.talent.v4.Job] will include all fields,
945974
// which can yield a very large response.

0 commit comments

Comments
 (0)