package dolt.services.remotesapi.v1alpha1

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

service ChunkStoreService

chunkstore.proto:23

service CredentialsService

credentials.proto:21

message ChunkTableInfo

chunkstore.proto:186

Used in: AddTableFilesRequest, CommitRequest

message ClientRepoFormat

chunkstore.proto:251

Used in: AddTableFilesRequest, CommitRequest, GetRepoMetadataRequest

message DownloadLoc

chunkstore.proto:106

Used in: GetDownloadLocsResponse

message GetDownloadLocsRequest

chunkstore.proto:126

Used as request type in: ChunkStoreService.GetDownloadLocations, ChunkStoreService.StreamDownloadLocations

message GetDownloadLocsResponse

chunkstore.proto:134

Used as response type in: ChunkStoreService.GetDownloadLocations, ChunkStoreService.StreamDownloadLocations

message HttpGetChunk

chunkstore.proto:83

Used in: DownloadLoc

message HttpGetRange

chunkstore.proto:101

Used in: DownloadLoc

message HttpPostTableFile

chunkstore.proto:115

Used in: UploadLoc

enum ManifestAppendixOption

chunkstore.proto:295

Used in: AddTableFilesRequest

enum PushConcurrencyControl

chunkstore.proto:229

A ChunkStore can request a client to implement a specific concurrency control mechanism when updating a branch HEAD. This exists because passive remotes, like DoltHub, typically do not have meaningful workingSets. When a client requests to push a branch HEAD to a DoltHub remote, they have no visibility into the workingSet/ value for the corresponding branch. It has historically been the case that clients ignore it and just push the branch HEAD. On the other hand, when pushing to a running sql-server, not stomping concurrent transaction is important, and the remote endpoint will want the pushing client to ensure that it both checks that the branch's working set is clean and that it updates the branch's working set appropriately if the push is successful. Servers advertise which concurrency control mechanism they want in their GetRepoMetadataResponse.

Used in: GetRepoMetadataResponse

message RangeChunk

chunkstore.proto:88

Used in: HttpGetRange

message RefreshTableFileUrlRequest

chunkstore.proto:272

Used as request type in: ChunkStoreService.RefreshTableFileUrl

Used as field type in: DownloadLoc, TableFileInfo

message RepoId

chunkstore.proto:64

RepoId is how repositories are represented on dolthub, for example `dolthub/us-housing-prices-v2` has org = dolthub, repo_name = us-housing-prices-v2. All methods of ChunkStoreService targeting a repository take a RepoId. Many will also take a `repo_token`, which can be provided in addition to a RepoId. `repo_token`s can be returned from repository-accessing RPCs on ChunkStoreService, and providing them instead of RepoId for future calls to ChunkStoreService can be more efficient than providing RepoId itself. `repo_token`s are fully opaque to the client.

Used in: AddTableFilesRequest, CommitRequest, GetDownloadLocsRequest, GetRepoMetadataRequest, GetUploadLocsRequest, HasChunksRequest, ListTableFilesRequest, RebaseRequest, RefreshTableFileUrlRequest, RootRequest

message TableFileDetails

chunkstore.proto:140

Used in: GetUploadLocsRequest

message TableFileInfo

chunkstore.proto:264

Used in: ListTableFilesResponse

message UploadLoc

chunkstore.proto:119

Used in: GetUploadLocsResponse