File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed
docs/v3/codecs/sharding-indexed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -84,7 +84,7 @@ Configuration parameters
8484Sharding can be configured per array in the :ref: `array-metadata ` as follows::
8585
8686 {
87- codecs: [
87+ " codecs" : [
8888 {
8989 "name": "sharding_indexed"
9090 "configuration": {
@@ -110,7 +110,7 @@ Sharding can be configured per array in the :ref:`array-metadata` as follows::
110110 "endian": "little",
111111 }
112112 },
113- { "name": "crc32c"}
113+ { "name": "crc32c" }
114114 ]
115115 }
116116 }
@@ -235,7 +235,7 @@ common optimizations.
235235 read the entire value from the store into a byte buffer, (b) parse the shard
236236 index as specified above from the end of the buffer and (c) cut out the
237237 relevant bytes that belong to the requested chunk. The relevant bytes are
238- determined by the `offset,nbytes ` pair in the shard index. This bytestream
238+ determined by the `` offset,nbytes ` ` pair in the shard index. This bytestream
239239 then needs to be decoded with the inner codecs as specified in the sharding
240240 configuration applying the :ref: `decoding_procedure `. This is similar to how
241241 an implementation would access a sub-slice of a chunk.
You can’t perform that action at this time.
0 commit comments