I think the memstoreTS is stored with each KV (until it can be proven to be not needed - because no older open scanners, in which case it is not written during the next compaction and assumed 0) "Mild passing interest" :) Yep.
________________________________ From: Stack <[email protected]> To: [email protected]; lars hofhansl <[email protected]> Sent: Tuesday, August 28, 2012 11:54 AM Subject: Re: Disk space usage of HFilev1 vs HFilev2 On Tue, Aug 28, 2012 at 11:42 AM, lars hofhansl <[email protected]> wrote: > Are we terribly concerned about 3.5% of extra disk usage? > HFileV2 was designed to be more main memory efficient, which is in much > shorter supply than disk space (bloom filters and index blocks are > interspersed with data blocks and loaded when needed, etc) > I wouldn't get my knickers in a twist about 3.5% but a mild, passing interest, yes. > The stored MemstoreTS was introduced in 0.92, which also introduced HFileV2. > Yeah, IIRC, its a metadata field added to each storefile. St.Ack
