Introduce the key encoding version

[PragmaTwice]

Search before asking

• I had searched in the issues and found no similar issues.

Motivation

The current key encoding has some historical legacy issues, and we need to adjust it through some means while ensuring compatibility.

To do this, first we can persist a key encoding version in storage and read it during loading.

Solution

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[VasuDevrani]

I went through the codebase, can you confirm if i got it right?

• the key encoding logic (encoding and decoding) is implemented in the InternalKey class
• can be fixed by introducing a new variable for encoding version, a function to read it from storage during loading process, update InternalKey class to handle different versions

[VasuDevrani]

/assign

[PragmaTwice]

I went through the codebase, can you confirm if i got it right?

• the key encoding logic (encoding and decoding) is implemented in the InternalKey class
• can be fixed by introducing a new variable for encoding version, a function to read it from storage during loading process, update InternalKey class to handle different versions

Yeah you are right.