davidradl commented on code in PR #26107: URL: https://github.com/apache/flink/pull/26107#discussion_r1944965145
########## docs/layouts/shortcodes/generated/forst_configurable_configuration.html: ########## @@ -0,0 +1,168 @@ +<table class="configuration table table-bordered"> + <thead> + <tr> + <th class="text-left" style="width: 20%">Key</th> + <th class="text-left" style="width: 15%">Default</th> + <th class="text-left" style="width: 10%">Type</th> + <th class="text-left" style="width: 55%">Description</th> + </tr> + </thead> + <tbody> + <tr> + <td><h5>state.backend.forst.block.blocksize</h5></td> + <td style="word-wrap: break-word;">4 kb</td> + <td>MemorySize</td> + <td>The approximate size (in bytes) of user data packed per block. The default blocksize is '4KB'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.block.cache-size</h5></td> + <td style="word-wrap: break-word;">8 mb</td> + <td>MemorySize</td> + <td>The amount of the cache for data blocks in ForSt. The default block-cache size is '8MB'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.block.metadata-blocksize</h5></td> + <td style="word-wrap: break-word;">4 kb</td> + <td>MemorySize</td> + <td>Approximate size of partitioned metadata packed per block. Currently applied to indexes block when partitioned index/filters option is enabled. The default blocksize is '4KB'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.bloom-filter.bits-per-key</h5></td> + <td style="word-wrap: break-word;">10.0</td> + <td>Double</td> + <td>Bits per key that bloom filter will use, this only take effect when bloom filter is used. The default value is 10.0.</td> + </tr> + <tr> + <td><h5>state.backend.forst.bloom-filter.block-based-mode</h5></td> + <td style="word-wrap: break-word;">false</td> + <td>Boolean</td> + <td>If true, ForSt will use block-based filter instead of full filter, this only take effect when bloom filter is used. The default value is 'false'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.compaction.filter.periodic-compaction-time</h5></td> + <td style="word-wrap: break-word;">30 d</td> + <td>Duration</td> + <td>Periodic compaction could speed up expired state entries cleanup, especially for state entries rarely accessed. Files older than this value will be picked up for compaction, and re-written to the same level as they were before. It makes sure a file goes through compaction filters periodically. 0 means turning off periodic compaction.The default value is '30days'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.compaction.filter.query-time-after-num-entries</h5></td> + <td style="word-wrap: break-word;">1000</td> + <td>Long</td> + <td>Number of state entries to process by compaction filter before updating current timestamp. Updating the timestamp more often can improve cleanup speed, but it decreases compaction performance because it uses JNI calls from native code.The default value is '1000L'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.compaction.level.max-size-level-base</h5></td> + <td style="word-wrap: break-word;">256 mb</td> + <td>MemorySize</td> + <td>The upper-bound of the total size of level base files in bytes. The default value is '256MB'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.compaction.level.target-file-size-base</h5></td> + <td style="word-wrap: break-word;">64 mb</td> + <td>MemorySize</td> + <td>The target file size for compaction, which determines a level-1 file size. The default value is '64MB'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.compaction.level.use-dynamic-size</h5></td> + <td style="word-wrap: break-word;">false</td> + <td>Boolean</td> + <td>If true, ForSt will pick target size of each level dynamically. From an empty DB, ForSt would make last level the base level, which means merging L0 data into the last level, until it exceeds max_bytes_for_level_base. And then repeat this process for second last level and so on. The default value is 'false'. For more information, please refer to <a href="https://github.com/facebook/rocksdb/wiki/Leveled-Compaction#level_compaction_dynamic_level_bytes-is-true";>RocksDB's doc.</a></td> Review Comment: what do we man by DB here? RocksDB or Forst? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
