add additional tutorials #667
Conversation
|
|
||
| ==== Cypher syntax | ||
|
|
||
| All changes in the Cypher language syntax are detailed in link:https://neo4j.com/docs/cypher-manual/5/deprecations-additions-removals-compatibility[Cypher Manual -> Removals, deprecations, additions and extensions]. |
There was a problem hiding this comment.
Here, we refer to "Cypher Manual 5" https://neo4j.com/docs/cypher-manual/5/deprecations-additions-removals-compatibility/
There was a problem hiding this comment.
That is the latest version, I believe. Check with Jens.
There was a problem hiding this comment.
Yes! It looks like it! It says Version 5 (current) in version picker
There was a problem hiding this comment.
Cypher 5 is the latest until release of Cypher 25 later this year.
| All changes in the Cypher language syntax are detailed in link:https://neo4j.com/docs/cypher-manual/5/deprecations-additions-removals-compatibility[Cypher Manual -> Removals, deprecations, additions and extensions]. | ||
| Thoroughly review this section in the version you are moving to and make the necessary changes in your code. | ||
|
|
||
| Here is a short list of the main changes introduced in Neo4j 5: |
There was a problem hiding this comment.
Can we still refer to the changes in Neo4j 5 like this?
There was a problem hiding this comment.
No, it's Neo4j latest.
There was a problem hiding this comment.
But they weren't introduced in Neo4j latest - they were introduced in Neo4j 5
Maybe I can just drop the word introduced?
There was a problem hiding this comment.
@JPryce-Aklundh how would you approach this one?
There was a problem hiding this comment.
I would delete this, and just have a link to the page mentioned above. You have only listed changes that were added in 5.0 - but what about 5.1, 5.2 etc? and regardless, what users will care about is feature removals, is anything. So, I ould say this
"For a full list of features removed in Neo4j 5.0, see (link here: https://development.neo4j.dev/docs/cypher-manual/current/deprecations-additions-removals-compatibility/#_removed_features_2).
(Only 5.0 made breaking changes, more will come with the release coinciding with the release of whatever release coincides with Cypher 25).
There was a problem hiding this comment.
We need to check how this works in Aura. A user shouldn't have to worry about Neo4j 5, I think that from their end, they go from 4.x to latest and skip over 5. Behind the scenes, they go via 5 though. The migration readiness report will tell them what to do though.
|
|
||
| ==== Cypher syntax | ||
|
|
||
| All changes in the Cypher language syntax are detailed in link:https://neo4j.com/docs/cypher-manual/5/deprecations-additions-removals-compatibility[Cypher Manual -> Removals, deprecations, additions and extensions]. |
There was a problem hiding this comment.
That is the latest version, I believe. Check with Jens.
| All changes in the Cypher language syntax are detailed in link:https://neo4j.com/docs/cypher-manual/5/deprecations-additions-removals-compatibility[Cypher Manual -> Removals, deprecations, additions and extensions]. | ||
| Thoroughly review this section in the version you are moving to and make the necessary changes in your code. | ||
|
|
||
| Here is a short list of the main changes introduced in Neo4j 5: |
There was a problem hiding this comment.
No, it's Neo4j latest.
Co-authored-by: Jessica Wright <[email protected]>
| === Indexes | ||
|
|
||
| In Neo4j latest version, BTREE indexes are replaced by RANGE, POINT, and TEXT indexes. | ||
| Before migrating a database, in Neo4j 4, you should create a matching RANGE, POINT, or TEXT index for each BTREE index (or index-backed constraint). |
There was a problem hiding this comment.
How can you do this before migrating? You cant create range indexes in Neo4j 4.4?
Also, text and point indexes are not replacements of btree - they add a functionality that btree didnt have.
|
|
||
| ==== Cypher syntax | ||
|
|
||
| All changes in the Cypher language syntax are detailed in link:https://neo4j.com/docs/cypher-manual/5/deprecations-additions-removals-compatibility[Cypher Manual -> Removals, deprecations, additions and extensions]. |
There was a problem hiding this comment.
Cypher 5 is the latest until release of Cypher 25 later this year.
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
| @@ -1,4 +1,4 @@ | |||
| = Migrating your Neo4j AuraDB Free instance to another AuraDB plan | |||
| = Upgrading your AuraDB Free instance to another AuraDB plan | |||
There was a problem hiding this comment.
This is a migration. You upgrade your plan, but the instance needs to be migrated.
| === Indexes | ||
|
|
||
| Neo4j 5 replaced b-tree indexes with link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/managing-indexes/#create-range-index[range indexes]. | ||
| Before migrating a database, in Neo4j 4, you should create a matching RANGE, POINT, or TEXT index for each b-tree index (or index-backed constraint). |
There was a problem hiding this comment.
How is this possible?
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
| This guarantees that Neo4j has full rights to start and work with the database files you use. | ||
|
|
||
| . Stop your self-managed Neo4j database. | ||
| If you are running AuraDB Virtual Dedicated Cloud or AuraDS Enterprise, you can stop only the database you want to dump using the command `STOP DATABASE {database}` in Cypher Shell or Browser. |
There was a problem hiding this comment.
It says to stop your self-managed database. AuraDB VDC and AuraDS Enterprise are not self-managed. You don't want to dump your Aura db, but your self-managed db.
Is the case that you have to stop the db you want to upload to as well, then we should say so explicitly.
There was a problem hiding this comment.
. Stop your Neo4j database.
If you are running AuraDB Virtual Dedicated Cloud or AuraDS Enterprise, you can stop the database you want to dump using the command STOP DATABASE Neo4j in Cypher Shell or Browser.
Docs say "STOP DATABASE" is "Not available on Aura" in the Cypher shells docs
https://neo4j.com/docs/operations-manual/current/database-administration/standard-databases/create-databases/
|
|
||
| === Indexes | ||
|
|
||
| BTREE indexes have been replaced by RANGE, POINT, and TEXT indexes. |
There was a problem hiding this comment.
Mayeb we should say in which version they were replaced?
There was a problem hiding this comment.
"BTREE indexes were replaced by RANGE, POINT, and TEXT indexes in Neo4j v5."
Co-authored-by: Jessica Wright <[email protected]>
|
This PR includes documentation updates New pages: Updated pages: |
No description provided.