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.

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

Revert "Fix parsing unknown fields breaks record deserialisation" #676

Merged

Conversation

idimov-keeper
Copy link
Collaborator

Reverts #666

// New/missing field: Polymorphic serializer was not found for class discriminator 'UNKNOWN'...
// New/missing field property (field def updated): Encountered unknown key 'UNKNOWN'.
// Avoid 'ignoreUnknownKeys = true' to prevent erasing new properties on save/update
println("Record ${record.recordUid} has unexpected data properties (ignored).\n"+
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This message is very confusing, is the gateway ahead OR behind? can we cahnge it something like this:

println("Record ${record.recordUid} contains unrecognized data properties and could not be fully parsed.\n" +
        "This may occur if the Keeper Secrets Manager (KSM) SDK version you're using is not compatible with the record's data schema.\n" +
        "Please ensure that you are using the latest version of the KSM SDK. If the issue persists, contact [email protected] for assistance.")

@maksimu maksimu merged commit 3f2e11e into release/sdk/java/core/v16.6.6 Nov 22, 2024
4 checks passed
@idimov-keeper idimov-keeper deleted the revert-666-fix/parsing-unknown-fields branch November 22, 2024 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants