Default package

Get desktop application:
View/edit binary Protocol Buffers messages

1. Primary Key: (C_W_ID, C_D_ID, C_ID) 2. (C_W_ID, C_D_ID) Foreign Key, references (D_W_ID, D_ID)

• uint64 C_ID = 1

  96,000 unique IDs 3,000 are populated per district

• uint32 C_D_ID = 2

  20 unique IDs

• uint64 C_W_ID = 3

  2*W unique IDs

• string C_FIRST = 4

  variable text, size 16

• string C_MIDDLE = 5

  fixed text, size 2

• string C_LAST = 6

  variable text, size 16

• string C_STREET_1 = 7

  variable text, size 20

• string C_STREET_2 = 8

  variable text, size 20

• string C_CITY = 9

  variable text, size 20

• string C_STATE = 10

  fixed text, size 2

• string C_ZIP = 11

  fixed text, size 9

• string C_PHONE = 12

  variable text, size 16

• uint64 C_SINCE = 13

  date and time

• string C_CREDIT = 14

  fixed text, size 2 "GC"=good, "BC"=bad

• double C_CREDIT_LIM = 15

  signed numeric (12,2)

• double C_DISCOUNT = 16

  signed numeric (4,4)

• double C_BALANCE = 17

  signed numeric (12,2)

• double C_YTD_PAYMENT = 18

  signed numeric (12,2) //year till date payment

• double C_PAYMENT_CNT = 19

  numeric(4)

• double C_DELIVERY_CNT = 20

  numeric(4)

• string C_DATA = 21

  variable text, size 500 Miscellaneous information

• uint64 W_ID = 1

  Primary Key: W_ID num = W, Warehouses are populated

• string W_NAME = 2

  variable text, size 10

• string W_STREET_1 = 3

  variable text, size 20

• string W_STREET_2 = 4

  variable text, size 20

• string W_CITY = 5

  variable text, size 20

• string W_STATE = 6

  fixed text, size 2

• string W_ZIP = 7

  fixed text, size 9

• double W_TAX = 8

  signed numeric (4,4) Sales tax

• double W_YTD = 9

  signed numeric (12,2) Year to date balance

• uint32 D_ID = 1

  20 unique IDs 10 are populated per warehouse

• uint64 D_W_ID = 2

  D_W_ID Foreign Key, references W_ID Primary Key: (D_W_ID, D_ID)

• string D_NAME = 3

  variable text, size 10

• string D_STREET_1 = 4

  variable text, size 20

• string D_STREET_2 = 5

  variable text, size 20

• string D_CITY = 6

  variable text, size 20

• string D_STATE = 7

  fixed text, size 2

• string D_ZIP = 8

  fixed text, size 9

• double D_TAX = 9

  signed numeric (4,4) Sales tax

• double D_YTD = 10

  signed numeric (12,2) Year to date balance

• uint64 D_NEXT_O_ID = 100

  10,000,000 unique IDs Next available Order number

Primary Key: none (H_C_W_ID, H_C_D_ID, H _C_ID) Foreign Key, references (C_W_ID, C_D_ID, C_ID) (H_W_ID, H _D_ID) Foreign Key, references (D_W_ID, D_ID) Comment: Rows in the History table do not have a primary key as, with in the context of the benchmark, there is no need to uniquely identify a row within this table. Note: The TPC-C application does not have to be capable of utilizing the in creased range of C_ID values beyond 6,000.

• uint64 H_C_ID = 1

  96,000 unique IDs 3,000 are populated per district

• uint32 H_C_D_ID = 2

  20 unique IDs

• uint64 H_C_W_ID = 3

  2*W unique IDs

• uint64 H_D_ID = 4

  20 unique IDs 10 are populated per warehouse

• uint64 H_W_ID = 5

  2*W, Warehouses are populated

• uint64 H_DATE = 6

  date and time

• double H_AMOUNT = 7

  signed numeric (6, 2)

• string H_DATA = 8

  variable text, size 24, Miscellaneous information

HashedRWSet encapsulates hashed representation of a private read-write set for KV or Document data model

• repeated KVReadHash hashed_reads = 1

• repeated KVWriteHash hashed_writes = 2

• repeated KVMetadataWriteHash metadata_writes = 3

Primary Key: I_ID

• uint64 I_ID = 1

• uint64 I_IM_ID = 2

  Image ID associated to Item

• string I_NAME = 3

• double I_PRICE = 4

• string I_DATA = 5

  Brand information

KVMetadataEntry captures a 'name'ed entry in the metadata of a key/key-hash.

Used in: KVMetadataWrite, KVMetadataWriteHash

• string name = 1

• bytes value = 2

KVMetadataWrite captures all the entries in the metadata associated with a key

Used in: KVRWSet

• string key = 1

• repeated KVMetadataEntry entries = 2

KVMetadataWriteHash captures all the upserts to the metadata associated with a key hash

Used in: HashedRWSet

• bytes key_hash = 1

• repeated KVMetadataEntry entries = 2

KVRWSet encapsulates the read-write set for a chaincode that operates upon a KV or Document data model This structure is used for both the public data and the private data

• repeated KVRead reads = 1

• repeated RangeQueryInfo range_queries_info = 2

• repeated KVWrite writes = 3

• repeated KVMetadataWrite metadata_writes = 4

KVRead captures a read operation performed during transaction simulation A 'nil' version indicates a non-existing key read by the transaction

Used in: KVRWSet, QueryReads, comm.QueryResult

• string table = 1

• string key = 2

• bytes value = 3

KVReadHash is similar to the KVRead in spirit. However, it captures the hash of the key instead of the key itself version is kept as is for now. However, if the version also needs to be privacy-protected, it would need to be the hash of the version and hence of 'bytes' type

Used in: HashedRWSet

• bytes key_hash = 1

• optional Version version = 2

KVWrite captures a write (update/delete) operation performed during transaction simulation

Used in: KVRWSet

• string table = 1

• string key = 2

• bytes value = 3

• bool is_delete = 4

KVWriteHash is similar to the KVWrite. It captures a write (update/delete) operation performed during transaction simulation

Used in: HashedRWSet

• bytes key_hash = 1

• bool is_delete = 2

• bytes value_hash = 3

Primary Key: (NO_W_ID, NO_D_ID, NO_O_ID) (NO_W_ID, NO_D_ID, NO_O_ID) Foreign Key, references (O_W_ID, O_D_ID, O_ID)

• uint64 NO_O_ID = 1

• uint32 NO_D_ID = 2

• uint64 NO_W_ID = 3

Primary Key: (O_W_ID, O_D_ID, O_ID) (O_W_ID, O_D_ID, O_C_ID) Foreign Key, references (C_W_ID, C_D_ID, C_ID)

• uint64 O_ID = 1

• uint32 O_D_ID = 2

• uint64 O_W_ID = 3

• uint64 O_C_ID = 4

• uint64 O_ENTRY_D = 5

  date and time

• uint32 O_CARRIER_ID = 6

• uint32 O_OL_CNT = 7

  Count of Order-Lines

• uint32 O_ALL_LOCAL = 8

Primary Key: (OL_W_ID, OL_D_ID, OL_O_ID, OL_NUMBER) (OL_W_ID, OL_D_ID, OL_O_ID) Foreign Key, references (O_W_ID, O_D_ID, O_ID) (OL_SUPPLY_W_ID, OL_I_ID) Foreign Key, references (S_W_ID, S_I_ID)

• uint64 OL_O_ID = 1

• uint32 OL_D_ID = 2

• uint64 OL_W_ID = 3

• uint32 OL_NUMBER = 4

• uint64 OL_I_ID = 5

• uint64 OL_SUPPLY_W_ID = 6

• uint64 OL_DELIVERY_D = 7

  date and time, or nil

• uint32 OL_QUANTITY = 8

• double OL_AMOUNT = 9

• string OL_DIST_INFO = 10

QueryReads encapsulates the KVReads for the items read by a transaction as a result of a query execution

Used in: RangeQueryInfo

• repeated KVRead kv_reads = 1

QueryReadsMerkleSummary encapsulates the Merkle-tree hashes for the QueryReads This allows to reduce the size of RWSet in the presence of query results by storing certain hashes instead of actual results. maxDegree field refers to the maximum number of children in the tree at any level maxLevel field contains the lowest level which has lesser nodes than maxDegree (starting from leaf level)

Used in: RangeQueryInfo

• uint32 max_degree = 1

• uint32 max_level = 2

• repeated bytes max_level_hashes = 3

RangeQueryInfo encapsulates the details of a range query performed by a transaction during simulation. This helps protect transactions from phantom reads by varifying during validation whether any new items got committed within the given range between transaction simuation and validation (in addition to regular checks for updates/deletes of the existing items). readInfo field contains either the KVReads (for the items read by the range query) or a merkle-tree hash if the KVReads exceeds a pre-configured numbers

Used in: KVRWSet

• string start_key = 1

• string end_key = 2

• bool itr_exhausted = 3

• oneof reads_info

  • QueryReads raw_reads = 4

  • QueryReadsMerkleSummary reads_merkle_hashes = 5

Primary Key: (S_W_ID, S_I_ID) S_W_ID Foreign Key, references W_ID S_I_ID Foreign Key, references I_ID

• uint64 S_I_ID = 1

  100,000 populated per warehouse

• uint64 S_W_ID = 2

• int64 S_QUANTITY = 3

• repeated string S_DIST = 4

• uint64 S_YTD = 5

• uint64 S_ORDER_CNT = 6

• uint64 S_REMOTE_CNT = 7

• string S_DATA = 8

TransactionPayload binds a proposal to its action. The type field in the header dictates the type of action to be applied to the ledger.

• bytes header = 1

  The header of the proposal action, which is the proposal header

• bytes payload = 2

  The payload of the action as defined by the type in the header For chaincode, it's the bytes of ChaincodeActionPayload

• uint64 nonce = 3

  Using nonce to assure signature is different for each transaction

• bytes digest = 4

  User digest, generate when this field is empty

• VALID = 0

• NIL_ENVELOPE = 1

• BAD_PAYLOAD = 2

• BAD_COMMON_HEADER = 3

• BAD_CREATOR_SIGNATURE = 4

• INVALID_ENDORSER_TRANSACTION = 5

• INVALID_CONFIG_TRANSACTION = 6

• UNSUPPORTED_TX_PAYLOAD = 7

• BAD_PROPOSAL_TXID = 8

• DUPLICATE_TXID = 9

• ENDORSEMENT_POLICY_FAILURE = 10

• MVCC_READ_CONFLICT = 11

• PHANTOM_READ_CONFLICT = 12

• UNKNOWN_TX_TYPE = 13

• TARGET_CHAIN_NOT_FOUND = 14

• MARSHAL_TX_ERROR = 15

• NIL_TXACTION = 16

• EXPIRED_CHAINCODE = 17

• CHAINCODE_VERSION_CONFLICT = 18

• BAD_HEADER_EXTENSION = 19

• BAD_CHANNEL_HEADER = 20

• BAD_RESPONSE_PAYLOAD = 21

• BAD_RWSET = 22

• ILLEGAL_WRITESET = 23

• INVALID_WRITESET = 24

• INVALID_CHAINCODE = 25

• NOT_VALIDATED = 254

• INVALID_OTHER_REASON = 255

Version encapsulates the version of a Key A version of a committed key is maintained as the height of the transaction that committed the key. The height is represenetd as a tuple <blockNum, txNum> where the txNum is the position of the transaction (starting with 0) within block

Used in: KVReadHash

• uint64 block_num = 1

• uint64 tx_num = 2

• uint64 W_ID = 1

  Primary Key: W_ID num = W, Warehouses are populated

• string W_NAME = 2

  variable text, size 10

• string W_STREET_1 = 3

  variable text, size 20

• string W_STREET_2 = 4

  variable text, size 20

• string W_CITY = 5

  variable text, size 20

• string W_STATE = 6

  fixed text, size 2

• string W_ZIP = 7

  fixed text, size 9

• double W_TAX = 8

  signed numeric (4,4) Sales tax

• double W_YTD = 9

  signed numeric (12,2) Year to date balance

• repeated YCSB_FOR_BLOCK_BENCH.YCSB_FOR_BLOCK_BENCH_PAIR values = 1

Used in: YCSB_FOR_BLOCK_BENCH

• bytes key = 1

• bytes value = 2

• repeated bytes reads = 1

• repeated bytes update = 2

• bytes table = 3