regen query data resolvers-by-hash
Query resolvers with registered data by the ContentHash of the data
Synopsis
Query resolvers with registered data by the ContentHash of the data with optional pagination flags.
regen query data resolvers-by-hash [hash-json] [flags]
Examples
regen q data resolvers-by-hash hash.json
regen q data resolvers-by-hash hash.json --limit 10 --count-total
where hash.json contains:
{
"graph": {
"hash": "YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=",
"digest_algorithm": "DIGEST_ALGORITHM_BLAKE2B_256",
"canonicalization_algorithm": "GRAPH_CANONICALIZATION_ALGORITHM_URDNA2015",
"merkle_tree": "GRAPH_MERKLE_TREE_NONE_UNSPECIFIED"
}
}
Options
--count-total count total number of records in resolvers-by-hash to query for
--grpc-addr string the gRPC endpoint to use for this chain
--grpc-insecure allow gRPC over insecure channels, if not TLS the server must use TLS
--height int Use a specific height to query state at (this can error if the node is pruning state)
-h, --help help for resolvers-by-hash
--limit uint pagination limit of resolvers-by-hash to query for (default 100)
--node string <host>:<port> to Tendermint RPC interface for this chain (default "tcp://localhost:26657")
--offset uint pagination offset of resolvers-by-hash to query for
-o, --output string Output format (text|json) (default "text")
--page uint pagination page of resolvers-by-hash to query for. This sets offset to a multiple of limit (default 1)
--page-key string pagination page-key of resolvers-by-hash to query for
--reverse results are sorted in descending order
Options inherited from parent commands
--chain-id string The network chain ID
SEE ALSO
- regen query data - Query commands for the data module