Question: Badger key version consistency among raft followers

ozan · August 17, 2020, 9:53pm

dgraph-io/badger/blob/4c8fe7fd63e36f9e39b788c084e18e293413a71d/options.go#L277-L285


// WithNumVersionsToKeep returns a new Options value with NumVersionsToKeep set to the given value.
//
// NumVersionsToKeep sets how many versions to keep per key at most.
//
// The default value of NumVersionsToKeep is 1.
func (opt Options) WithNumVersionsToKeep(val int) Options {
	opt.NumVersionsToKeep = val
	return opt
}

Badger internally keeps versions as uint64 but options only accepts int type. Is there are specific reason for this? In documentation it says dgraph sets infinity to versions. This option lets upper bound be platform dependent. Is it possible to make it consistent and make Options.NumVersionsToKeep be uint64?
Cheers.

Topic		Replies	Views
Keeping key version when adding same key on the same transaction Badger kind:question	3	660	September 24, 2020
Badger keeping n+1 versions when using WithNumVersionsToKeep(n) Badger	3	534	November 23, 2020
Badger Documentation limited or Feature removed? Badger kind:question , status:accepted	10	753	December 21, 2020
Using badger for multiple version store Badger	6	1588	April 9, 2019
Request option to write multiple versions in a single batch Badger	3	965	April 5, 2021

Question: Badger key version consistency among raft followers

Related topics