Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Incompatible changes to key generation #453

Open
jpicht opened this issue Oct 11, 2024 · 1 comment
Open

Incompatible changes to key generation #453

jpicht opened this issue Oct 11, 2024 · 1 comment

Comments

@jpicht
Copy link

jpicht commented Oct 11, 2024 •
edited
Loading

Hi, I am currently trying to upgrade some very old programs to newer client versions, so we can finally get rid of predexp and update our clusters. The only possible client versions to bridge the gap, having support for both predexp and the new expressions, seem to be the 5.x versions.

Sadly these versions introduce incompatible changes in the key generation:

7b4c9a5 seems to remove the ability to use a []string value as a key. There seems to be no way to generate the same key in newer clients, making old data inaccessible.

How is one supposed to access data in newer versions, written with those kind of keys?

Also: can you please explain why this was removed? I cannot find any documentation on this.
@khaf
Copy link
Collaborator

khaf commented Oct 14, 2024

This was removed based on strict requirements from product, enforced by the server. I kept them going for a while, but at some point the client had to become compliant.
It is still possible to generate those keys, you just have to compute the digest yourself and use Key.SetDigest() method to assign it. Not sure if you can send the original key to the server though, since it will be rejected IIRC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@khaf @jpicht