package com.vmware.concord.thin_replica

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc ReadState (ReadStateRequest, stream Data)

  thin_replica.proto:28

  Finite stream which sends the current state that is visible to the Thin Replica client

  message ReadStateRequest

  thin_replica.proto:50

  (message has no fields)

• rpc ReadStateHash (ReadStateHashRequest, Hash)

  thin_replica.proto:31

  Return the hash of the state at a given block id

  message ReadStateHashRequest

  thin_replica.proto:52

  • oneof request

    • EventsRequest events = 1

    • EventGroupsRequest event_groups = 2

• rpc SubscribeToUpdates (SubscriptionRequest, stream Data)

  thin_replica.proto:35

  An endless stream of updates The client needs to acknowledge the received updates (AckUpdate) in order to help the server manage data growth

• rpc AckUpdate (BlockId, google.protobuf.Empty)

  thin_replica.proto:38

  The client acknowledges the receipt of updates based on the given block id

  message BlockId

  thin_replica.proto:71

  • uint64 block_id = 1

    TODO: signature

• rpc SubscribeToUpdateHashes (SubscriptionRequest, stream Hash)

  thin_replica.proto:42

  An endless stream of hashes of updates The client can use those hashes to verify the integrity of the data from the other stream

• rpc Unsubscribe (google.protobuf.Empty, google.protobuf.Empty)

  thin_replica.proto:47

  Cancel the stream gracefully The server will forget the acknowledgements, meaning data can be pruned Note: At any given point in time, the client should have only _one_ stream per server open

Used as response type in: ThinReplica.ReadState, ThinReplica.SubscribeToUpdates

• oneof data

  • Events events = 1

  • EventGroup event_group = 2

Used in: Data

• uint64 id = 1

• repeated bytes events = 2

• optional google.protobuf.Timestamp record_time = 3

• bytes trace_context = 4

Used in: Hash

• uint64 event_group_id = 1

• bytes hash = 2

See event.proto for documentation on EventGroups. Note: We don't want to depend on event.proto because any change to event.proto would result in a change for the TRS and therefore the replica itself. By keeping them separate we will have an easier time changing/maintaining those two interfaces.

Used in: ReadStateHashRequest, SubscriptionRequest

• uint64 event_group_id = 1

Used in: Data

• uint64 block_id = 1

  The data was found in this block

• repeated KVPair data = 2

• string correlation_id = 3

• bytes span_context = 4

Used in: Hash

• uint64 block_id = 1

• bytes hash = 2

Used in: ReadStateHashRequest, SubscriptionRequest

• uint64 block_id = 1

  Subscribe from (including) the given block id

Used as response type in: ThinReplica.ReadStateHash, ThinReplica.SubscribeToUpdateHashes

• oneof hash

  • EventsHash events = 1

  • EventGroupHash event_group = 2

Used in: Events

• bytes key = 1

• bytes value = 2

Used as request type in: ThinReplica.SubscribeToUpdateHashes, ThinReplica.SubscribeToUpdates

• oneof request

  • EventsRequest events = 1

  • EventGroupsRequest event_groups = 2

This message is used for *legacy updates* and in *serialized* form only. In addition, the message is used *only* as the interface between TRC and its consumer. See event_update.hpp for the complete data that is transferred to the caller.

• map<string, string> key_values = 1