Class: Google::Apis::CloudsearchV1::MessageAdded

Inherits:
Object
  • Object
show all
Includes:
Google::Apis::Core::Hashable, Google::Apis::Core::JsonObjectSupport
Defined in:
lib/google/apis/cloudsearch_v1/classes.rb,
lib/google/apis/cloudsearch_v1/representations.rb,
lib/google/apis/cloudsearch_v1/representations.rb

Overview

A message was added. Specifying id and initial labels.

Instance Attribute Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(**args) ⇒ MessageAdded

Returns a new instance of MessageAdded.



14164
14165
14166
# File 'lib/google/apis/cloudsearch_v1/classes.rb', line 14164

def initialize(**args)
   update!(**args)
end

Instance Attribute Details

#attribute_idsArray<String>

Corresponds to the JSON property attributeIds

Returns:

  • (Array<String>)


14121
14122
14123
# File 'lib/google/apis/cloudsearch_v1/classes.rb', line 14121

def attribute_ids
  @attribute_ids
end

#label_idsArray<String>

Corresponds to the JSON property labelIds

Returns:

  • (Array<String>)


14126
14127
14128
# File 'lib/google/apis/cloudsearch_v1/classes.rb', line 14126

def label_ids
  @label_ids
end

#message_keyGoogle::Apis::CloudsearchV1::MultiKey

A union-like type for identifiying an object in storage. MultiKeys contain multiple key fields, each in a separate key space. At least one key field must be set. More than one key field may be set as long as all key values refer to the same object. All objects in storage have unique server_id keys. All MultiKeys returned from storage to storage clients will always have the server_id field set. When creating an object, if a MultiKey without a server_id is supplied to storage, the storage system will auto-assign a server ID to the new object. For all other storage requests (i.e. those not creating new objects), clients may omit server_id (as long as they supply another key). Instead of server ids, clients can specify string based client_assigned_perm_id keys. Mail message drafts are a prime example of these kinds of objects. Each time a user saves a new version of a draft, the storage system needs to create a new object with the updated draft content and needs to delete the object containing the old content. The new object gets a new SERVER_ID but should get the same CLIENT_ASSIGNED_PERM_ID as the now-deleted object containing the old content. Carrying forward the perm ID allows it to be used to consistently refer to the same logical object across revisions. These perm IDs save sync clients from having to deal with changing object IDs. For example, assume there's a mail message in storage with SERVER_ID = 123 and CLIENT_ASSIGNED_PERM_ID = "foo". The following are all valid ways of addressing the object using MultiKeys: 1) MultiKey server_id = 123 2) MultiKey server_id = 123, client_assigned_perm_id = "foo" 3) MultiKey client_assigned_perm_id = "foo" Multikeys are never serialized in the storage. The individual keys are extracted and processed separately. Both the integer ids as well as string ids are indexed for efficient retrieval using the same fields in the backend. See go/tingle-multikeys for more information on background and motivation. Corresponds to the JSON property messageKey



14157
14158
14159
# File 'lib/google/apis/cloudsearch_v1/classes.rb', line 14157

def message_key
  @message_key
end

#sync_idsArray<Fixnum>

Note that there can be fewer sync ids than label ids. Corresponds to the JSON property syncIds

Returns:

  • (Array<Fixnum>)


14162
14163
14164
# File 'lib/google/apis/cloudsearch_v1/classes.rb', line 14162

def sync_ids
  @sync_ids
end

Instance Method Details

#update!(**args) ⇒ Object

Update properties of this object



14169
14170
14171
14172
14173
14174
# File 'lib/google/apis/cloudsearch_v1/classes.rb', line 14169

def update!(**args)
  @attribute_ids = args[:attribute_ids] if args.key?(:attribute_ids)
  @label_ids = args[:label_ids] if args.key?(:label_ids)
  @message_key = args[:message_key] if args.key?(:message_key)
  @sync_ids = args[:sync_ids] if args.key?(:sync_ids)
end