[SERVER-17924] Pretty print WiredTiger collection/index creation settings Created: 08/Apr/15  Updated: 12/May/17  Resolved: 12/May/17

Status: Closed
Project: Core Server
Component/s: Shell, WiredTiger
Affects Version/s: 3.0.1
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Luke Prochazka Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:

 Description   

The collection metadata records the collection compression type and the information is available in the collection statistics report

db.collection.stats()

However, there isn't an exact shell command to extract these values programmatically.

This request is to add support for exposing those statistics directly.



 Comments   
Comment by Justin Cohler [ 12/May/17 ]

This is not a priority on the Platforms team roadmap, and we do not plan to prioritize this work in the future.

Comment by Daniel Pasette (Inactive) [ 08/Apr/15 ]

I'm assuming this request is to prettyPrint the configuration options? All the creation options are listed in the stats, they're just not well formatted. You can see the compression is indicated by "block_compressor=snappy" in the example below. Agree this is not user friendly.

> db.startup_log.stats().wiredTiger.creationString
allocation_size=4KB,app_metadata=(formatVersion=1),block_allocation=best,block_compressor=snappy,cache_resident=0,checkpoint=,checkpoint_lsn=,checksum=uncompressed,collator=,columns=,dictionary=0,format=btree,huffman_key=,huffman_value=,id=3,internal_item_max=0,internal_key_max=0,internal_key_truncate=,internal_page_max=4KB,key_format=q,key_gap=10,leaf_item_max=0,leaf_key_max=0,leaf_page_max=32KB,leaf_value_max=1MB,memory_page_max=10m,os_cache_dirty_max=0,os_cache_max=0,prefix_compression=0,prefix_compression_min=4,split_deepen_min_child=0,split_deepen_per_child=0,split_pct=90,value_format=u,version=(major=1,minor=1)

Generated at Thu Feb 08 03:46:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.