Author: Darth Emmett
UniversalsearchNewPackerKnowledgeResultSupport
Information about the result support for a given interpretation.
UrlPoisoningData
Url poisoning information. This information is sparse: if num_spam_siblings is not populated, none of the following fields will be populated. Next tag: 6
VendingConsumerProtoTrustedGenomeAnnotation
—————————————————————————— Proto message containing the trusted genome entities that belong to an app. Document type: ANDROID_APP See go/gd-server-design for more info. ## Next tag: 4
VendingConsumerProtoTrustedGenomeHierarchy
Proto message containing one or multiple trusted genome entity. This is used to capture entities that belong to the same type and have parent-children relationship in the taxonomy. e.g. One hierarchy may include 3 entities with Game_Taxonomy Type: (1) Action (Level 1) (2) Platformer (Level 2 under Action) (3) Endless Runner (Level 3 under Platformer) e.g. One hierarchy may also include only 1 entity with Game_Graphic_Style: (1) Anime (No level information) Next ID: 5
TravelFlightsAirlineConfigLocalizedContactInfo
Airline contact info grouped by language. The language locale subcode will determine the country.
TravelFlightsNameCatalogProto
TrawlerClientServiceInfoClientLabels
ClientLabels contains client-specified key/value pairs, used to annotate individual FetchRequests and FetchReplies. This is primarily useful when the Multiverse Nexus performs postprocessing of fetchreplies. ClientLabels essentially allow clients to use the Nexus UI to slice statistics computed on fetchreplies by the specified key/value pairs. Note: we don’t use "map" type here delibrately in order to avoid the non-deterministric serialization of the "map" field. See b/69064361 for more details.
TrawlerContentRangeInfo
Parsed version of a Content-Range field, which in http might look like: Content-Range: bytes 500-999/3156
TrawlerEvent
Event is for logging interesting events that happen during a url fetch. Interesting events include "fetch start", "url rejected", etc. The events are written to binary logs together with the request and reply messages. If the same event occurs multiple times consecutively, We record the time of the first three instances in EarliestTimeStamp but omit the rest. We keep track the total number of occurrences in NumOccurrences and the timestamp of the last occurrence is kept in TimeStamp field.