Merge dev into 5.x #2003
Merged
Merge dev into 5.x #2003
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: NataliaIvakina <[email protected]>
Co-authored-by: Reneta Popova <[email protected]>
I suppose this change is related to the [PR#25468](neo-technology/neo4j#25468). Should we add the label 'Introduced in 5.21'?
based on the PR neo-technology/neo4j#25745 See also neo-technology/neo4j#25885 --------- Co-authored-by: Reneta Popova <[email protected]>
…unning neo4j-admin database migrate (neo4j#1679)
…certificates (neo4j#1688) Servers act as both servers and clients, and will complain if they only have one of the modes
…o4j#1700) Co-authored-by: Reneta Popova <[email protected]>
@yirensum additional context - https://neo4j.atlassian.net/wiki/spaces/Cluster/pages/511606802/Lighthouse+GA+plan --------- Co-authored-by: NataliaIvakina <[email protected]> Co-authored-by: Reneta Popova <[email protected]> Co-authored-by: Neil Dewhurst <[email protected]>
Describe two new public metrics of lighthouse @yirensum additional context - https://neo4j.atlassian.net/wiki/spaces/Cluster/pages/511606802/Lighthouse+GA+plan --------- Co-authored-by: Reneta Popova <[email protected]>
@yirensum additional context - https://neo4j.atlassian.net/wiki/spaces/Cluster/pages/511606802/Lighthouse+GA+plan --------- Co-authored-by: NataliaIvakina <[email protected]> Co-authored-by: Reneta Popova <[email protected]>
This is the only mention of escaping with backticks that I found in the Operations manual. Cypher Manual PR: neo4j/docs-cypher#1111
…eo4j#1858) The Parquet file support for neo4j admin import will come out in on of the next minor versions as a preview feature. Depending on the feedback we get from customers and users, there will be definitely coming more (also to the docs). This is a quite defensive change to avoid promising too much but also pointing out that this feature exists at all ;) Because the feature itself is not merged yet, I added the DO NOT MERGE label. Please let us get this into a shape where we can just merge it after the feature went into the product, thanks. This supersedes neo4j#1850 --------- Co-authored-by: Gerrit Meier <[email protected]> Co-authored-by: Reneta Popova <[email protected]>
Add deprecation labels according to the test results
Cherry-picked from neo4j#1967 without extra flag got: ``` Failed to load database 'system': Database already exists: systemLoad failed for databases: 'system' Load failed for databases: 'system' ``` Co-authored-by: iamolegga <[email protected]>
Once merged, we need to create a redirect for _reference/procedures.adoc_ and the _reference/index.adoc_. --------- Co-authored-by: Reneta Popova <[email protected]> Co-authored-by: NataliaIvakina <[email protected]>
Teeny-tiny typo
In order to know which database the query is targeting, we do some parsing to find if there is a USE-clause (e.g. `USE db RETURN 1 AS result`). If the parsing fails, we are not able to figure out what database the query should be run at and therefor the field in the log will be <none>. Please let me know if I can improve the documentation with more details, I just don't want to put information to confuse the user even more.
…) (neo4j#1987) Small fix to render the deprecation label for the `dbms.cluster.discovery.type` config
Co-authored-by: NataliaIvakina <[email protected]>
…must not be changed (neo4j#1997)
Replaces neo4j#1984 --------- Co-authored-by: Phil Wright <[email protected]>
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
32 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.