This is the work plan for the development of verkv rfc. It has two implementing processes:
versioncf like the defaultcf in tikv-server @fredchenbj Put/BatchPut RPC interface, and implement tikv-server side logic Get/BatchGet RPC interface, and implement tikv-server logic. Here decode value in client-go. Here it needs to use the iterator of RocksDB to get all versions of the key, and filter needed numbers of key-value to returnMaxVerNum about VerKV's data, and add GC logic to implement the version recyclingGetNumWithSV/BatchGetNumWithSV RPC interface, and implement tikv-server logic. Here it needs to use the iterator of RocksDB to get all versions of the key and filter older versions of key-value to return. This interface also supports TTL functionScan related RPC functionality, like the scan of RawKV. It would return a range of key-value of needed versionsDelete related RPC functionality, like the delete of RawKV. If you are interested in the above tasks, comment and pick up one. Mentoring available.
I pick task "Add verkv proto file in repo kvproto".
i pick up task "Add a new CF versioncf like the defaultcf in tikv-server"
Can we quickly implement the verkv interface with unimplemented!() or whatever? Currently we can't update kvproto for BR in TiKV because of this.

@kennytm OK, I will do it tomorrow.
@kennytm see pr: https://github.com/tikv/tikv/pull/7449
@fredchenbj I will work on the task 'Add the Put/BatchPut RPC interface, and implement tikv-server side logic' Please mentor me for following items:
@hskang9 OK, I would have a discussion with you later on slack.
@fredchenbj any review for 3rd item in PR #8282?
Most helpful comment
@kennytm OK, I will do it tomorrow.