Get desktop application:
View/edit binary Protocol Buffers messages
Version string of the noms binary format for this repository. See types.NomsBinFormat.
Version string of the nbs format of this repository. See nbs.StorageVersion.
Approximate number of bytes required for storage of all currently-referenced repository table files.
Get the download locations for a list of chunk hashes. Deprecated. Use StreamDownloadLocations.
Get the download locations for a list of chunk hashes. Streaming to support large and incrementally available payloads. Results are generated as requests come in.
Get upload locations for a list of table file hashes. NOTE: We upload full table files but download individual chunks.
If set, this is a write for the manifest appendix, not just the manifest table file specs. The table files appearing in `chunk_table_info` are added to `specs` and are also set in the manifest appendix. If `appendix_option` is `SET`, then the value of the appendix becomes the full list provided in `chunk_table_info` and any prior specs in the appendix are removed from the manifest specs. If `append_option` is `APPEND`, then the supplied table files are added to the appendix and to specs.
(message has no fields)
Ex: "bheni"
Ex: "Brian Hendriks"
Ex: "brian@liquidata.co"
Used in:
,Used in:
, ,Used in:
Used as request type in: ChunkStoreService.GetDownloadLocations, ChunkStoreService.StreamDownloadLocations
Used as response type in: ChunkStoreService.GetDownloadLocations, ChunkStoreService.StreamDownloadLocations
Used in:
Used in:
Used in:
Used in:
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:
Used in:
Archive zStd dictionary spans are indicated with these fields. On the consumer side, the existence of a non-zero dictionary length indicates that the chunk is compressed using zStd. This implies that the chunkSource is an archive source. If the dictionary length is zero, the chunk is compressed using snappy compression (classic NOMS table file or journal chunk use snappy compression).
Used as request type in: ChunkStoreService.RefreshTableFileUrl
Used as field type in:
,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:
, , , , , , , , ,Used in:
Used in:
Used in: