Skip to content

Conversation

@Hunterness
Copy link
Contributor

@Hunterness Hunterness commented Apr 1, 2025

We updated the store column to not say --0.0 in 2025.04 (and backported to next release of 5.LTS as well), and the currentPrimariesCount/currentSecondariesCount to be null to match what the requested versions already did.

Also added the sentence about being null for composite on the columns where that was already the case.

Copy link
Collaborator

@renetapopova renetapopova left a comment

Choose a reason for hiding this comment

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

I left a suggestion. Otherwise, looks good.

@renetapopova
Copy link
Collaborator

We updated the store column to not say --0.0 in 2025.04

@Hunterness Where is this updated store column (that doesn't say --0.0 in 2025.04)? We need to mark the change with a label that it's available from 2025.04, but I don't see the change.

@neo-technology-commit-status-publisher
Copy link
Collaborator

neo-technology-commit-status-publisher commented Apr 7, 2025

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

@renetapopova renetapopova merged commit 77e41b2 into neo4j:dev Apr 7, 2025
8 checks passed
renetapopova added a commit to renetapopova/docs-operations that referenced this pull request Apr 7, 2025
…bases return null (neo4j#2212)

We updated the store column to not say `--0.0` in 2025.04 (and
backported to next release of 5.LTS as well), and the
currentPrimariesCount/currentSecondariesCount to be null to match what
the requested versions already did.

Also added the sentence about being null for composite on the columns
where that was already the case.

---------

Co-authored-by: Reneta Popova <[email protected]>
renetapopova added a commit to renetapopova/docs-operations that referenced this pull request Apr 7, 2025
…bases return null (neo4j#2212)

We updated the store column to not say `--0.0` in 2025.04 (and
backported to next release of 5.LTS as well), and the
currentPrimariesCount/currentSecondariesCount to be null to match what
the requested versions already did.

Also added the sentence about being null for composite on the columns
where that was already the case.

---------

Co-authored-by: Reneta Popova <[email protected]>
renetapopova added a commit that referenced this pull request Apr 7, 2025
…bases return null (#2212) (#2229)

Cherry-picked from #2212

Co-authored-by: Therese Magnusson <[email protected]>
renetapopova added a commit that referenced this pull request Apr 7, 2025
…bases return null (#2212) (#2228)

Cherry-picked from #2212

---------

Co-authored-by: Therese Magnusson <[email protected]>
@Hunterness Hunterness deleted the dev-show-comp-db-updates branch April 7, 2025 10:26
NataliaIvakina added a commit that referenced this pull request May 15, 2025
Removing `a` in the table header (see line 44 in the PR #2212) led to
the formatting issues: lists and code blocks are not rendered as they
should be.
This PR fixes those issues
NataliaIvakina added a commit to NataliaIvakina/docs-operations that referenced this pull request May 15, 2025
Removing `a` in the table header (see line 44 in the PR neo4j#2212) led to
the formatting issues: lists and code blocks are not rendered as they
should be.
This PR fixes those issues
NataliaIvakina added a commit to NataliaIvakina/docs-operations that referenced this pull request May 15, 2025
Removing `a` in the table header (see line 44 in the PR neo4j#2212) led to
the formatting issues: lists and code blocks are not rendered as they
should be.
This PR fixes those issues
NataliaIvakina added a commit to NataliaIvakina/docs-operations that referenced this pull request May 15, 2025
Removing `a` in the table header (see line 44 in the PR neo4j#2212) led to
the formatting issues: lists and code blocks are not rendered as they
should be.
This PR fixes those issues
NataliaIvakina added a commit that referenced this pull request May 15, 2025
Removing `a` in the table header (see line 44 in the PR #2212) led to
the formatting issues: lists and code blocks are not rendered as they
should be.
This PR fixes those issues
NataliaIvakina added a commit that referenced this pull request May 15, 2025
Removing `a` in the table header (see line 44 in the PR #2212) led to
the formatting issues: lists and code blocks are not rendered as they
should be.
This PR fixes those issues
NataliaIvakina added a commit that referenced this pull request May 15, 2025
Removing `a` in the table header (see line 44 in the PR #2212) led to
the formatting issues: lists and code blocks are not rendered as they
should be.
This PR fixes those issues
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.

4 participants