Skip to content

Conversation

@renetapopova
Copy link
Collaborator

No description provided.

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

This PR includes documentation updates
View the updated docs at https://neo4j-docs-operations-2231.surge.sh

Updated pages:

Store format introduced in: 5.0.0
Database name: healthcare
Database in use: false
Store format version: block-block-1.1
Copy link
Collaborator

Choose a reason for hiding this comment

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

If we provide example with the block format, should we label it 'Enterprise edition'?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Do you mean to label the example output?

Copy link
Collaborator

@NataliaIvakina NataliaIvakina Apr 7, 2025

Choose a reason for hiding this comment

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

I was thinking about labelling the whole example.
Now I think this would look weird.
I'm wondering if we need to clarify that we test Enterprise edition here. For example,

[source, shell]
----
bin/neo4j-admin database info healthcare
----
+
If you're using Neo4j Enterprise Edition, the output can be the following:
+
[results]
----
Database name:                healthcare
Database in use:              false
Store format version:         block-block-1.1
<....>
----

Copy link
Collaborator

@NataliaIvakina NataliaIvakina Apr 7, 2025

Choose a reason for hiding this comment

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

Or it is unnecessary and we don't have to go into much detail here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I could add a sentence before all examples to say, "The following examples assume that you are using Neo4j Enterprise edition."

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Hey @NataliaIvakina, I added two intro sentences. Could you please take a look if they make sense?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Perfect 👌 Looks great!

Copy link
Collaborator

@NataliaIvakina NataliaIvakina left a comment

Choose a reason for hiding this comment

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

Looks good!
I suppose you have tested everything 😄

@neo4j-docops-agent
Copy link
Collaborator

neo4j-docops-agent 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 6cd1313 into neo4j:dev Apr 8, 2025
8 checks passed
@renetapopova renetapopova deleted the dev-store-info branch April 8, 2025 09:38
renetapopova added a commit to renetapopova/docs-operations that referenced this pull request Apr 8, 2025
renetapopova added a commit to renetapopova/docs-operations that referenced this pull request Apr 8, 2025
renetapopova added a commit that referenced this pull request Apr 8, 2025
renetapopova added a commit that referenced this pull request Apr 8, 2025
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