Skip to content

Detailing downgrading of schema version - #335

Open
ahus1 wants to merge 1 commit into
keycloak:mainfrom
ahus1:detailing-downgrading-of-versions
Open

Detailing downgrading of schema version #335
ahus1 wants to merge 1 commit into
keycloak:mainfrom
ahus1:detailing-downgrading-of-versions

Conversation

@ahus1

@ahus1 ahus1 commented Jan 21, 2022

Copy link
Copy Markdown
Member

Scenario: write in mixed environment or downgrades.

This is following up on the discussion keycloak/keycloak#9640

@ahus1
ahus1 requested a review from hmlnarik January 21, 2022 13:15
@ahus1
ahus1 requested review from sguilhen and vramik January 21, 2022 13:15
@ahus1

ahus1 commented Jan 21, 2022

Copy link
Copy Markdown
Member Author

Reading the docs, I found the note in the docs:

For each of the entities [...], the current store version is the entity schema version that the store uses for writing objects.

I tried to add paragraphs and change one line to highlight:

  • the schema downgrading scenario
  • that "readability" implies that the data can later be written to the store again even on downgrades without the loss of (significant) information

Please let me know if this is helpful or confusing, and what is missing or could be shortened.

Thanks!

@sguilhen sguilhen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I personally think the suggested changes properly convey what was discussed and to me they make the document clearer.

@hmlnarik hmlnarik removed their assignment Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants