Merge branch 'dev' into kubernetes-backup-refactor

Author: bfeshti

modules/ROOT/pages/backup-restore/inspect.adoc

@@ -29,12 +29,17 @@ The metadata contains the following information:
 
 [source,role=noheader]
 ----
-neo4j-admin backup inspect [-h] [--empty] [--expand-commands] [--latest-backup]
-                           [--latest-chain] [--show-metadata] [--verbose]
-                           [--additional-config=<file>] [--database=<database>]
-                           [--format=<value>] <backup-path>
+neo4j-admin backup inspect [-h] [--empty] [--expand-commands] [--latest-backup] [--latest-chain]
+                           [--verbose] [--additional-config=<file>] [--database=<database>] [--format=<value>]
+                           <backup-path>
 ----
 
+[NOTE]
+====
+Starting with Neo4j 2025.07, the backup metadata is always shown by default when using the `neo4j-admin backup inspect` command.
+If you are on a previous version of Neo4j, you must specify the `--show-metadata` option to see the backup metadata.
+====
+
 === Description
 
 Command to read the backup metadata.
@@ -87,10 +92,6 @@ The `<backup-path>` parameter can also inspect backups stored in AWS S3 buckets,
 | List the full backup chain ending with the latest downloaded backup.
 | false
 
-| --show-metadata
-| Show the backup metadata.
-| false
-
 | --database=<database>
 | Name of the database to inspect.
 |
@@ -113,6 +114,12 @@ The `<backup-path>` parameter can also inspect backups stored in AWS S3 buckets,
 The `--latest-backup` and `--latest-chain` options cannot be used together.
 ====
 
+[NOTE]
+====
+Starting with Neo4j 2025.07, the `--show-metadata` option is deprecated and ignored.
+The backup metadata is always shown by default when using the `neo4j-admin backup inspect` command.
+However, if you are on a previous version of Neo4j, you must specify the `--show-metadata` option to see the backup metadata.
+====
 
 [[aggregate-backup-example]]
 == Examples
@@ -140,7 +147,7 @@ The following command lists the backup files' names along with their respective
 
 [source,shell]
 ----
-bin/neo4j-admin backup inspect /backups --show-metadata --empty
+bin/neo4j-admin backup inspect /backups --empty
 ----
 
 The `--empty` option is used to include the empty backups.
@@ -163,13 +170,19 @@ Empty backups are used to record the backup history.
 | file:///backups/london-2024-10-07T16-03-51.backup |   london | d4dae73c-dfef-4d28-88cd-fe6cc88ddca1 | 2024-10-07T16:03:51 |  true |       true |         1 |          5 |      true |
 ----
 
+[NOTE]
+====
+Starting with Neo4j 2025.07, the backup metadata is always shown by default when using the `neo4j-admin backup inspect` command.
+If you are on a previous version of Neo4j, you must specify the `--show-metadata` option to see the backup metadata.
+====
+
 === Listing the latest backups
 
 To list only the most recent backups performed for each database, use the `--latest-backup` option.
 
 [source,shell]
 ----
-bin/neo4j-admin backup inspect /backups --show-metadata --latest-backup
+bin/neo4j-admin backup inspect /backups --latest-backup
 ----
 
 .Example output
@@ -181,14 +194,20 @@ bin/neo4j-admin backup inspect /backups --show-metadata --latest-backup
 | file:///backups/london-2024-10-07T16-04-05.backup |   london | d4dae73c-dfef-4d28-88cd-fe6cc88ddca1 | 2024-10-07T16:04:05 | false |       true |         6 |          6 |     false |
 ----
 
+[NOTE]
+====
+Starting with Neo4j 2025.07, the backup metadata is always shown by default when using the `neo4j-admin backup inspect` command.
+If you are on a previous version of Neo4j, you must specify the `--show-metadata` option to see the backup metadata.
+====
+
 === Inspecting backup chains
 
 A backup chain corresponds to a sequence of one or more backup(s) logically connected by their transaction IDs.
 To inspect the backup chains of a given database, use the `--latest-chain` option and the `--database` option with the database whose backup chain you want to inspect:
 
 [source,shell]
 ----
-bin/neo4j-admin backup inspect /backups --show-metadata --latest-chain --database=london
+bin/neo4j-admin backup inspect /backups --latest-chain --database=london
 ----
 
 .Example output
@@ -206,14 +225,19 @@ The result returns a chain of size two:
 Those modifications are materialised by a sequence of transactions to apply.
 Its range is [6,6].
 
+[NOTE]
+====
+Starting with Neo4j 2025.07, the backup metadata is always shown by default when using the `neo4j-admin backup inspect` command.
+If you are on a previous version of Neo4j, you must specify the `--show-metadata` option to see the backup metadata.
+====
 
 === Inspecting a backup chain ending with a specific backup
 
 To inspect a backup chain ending with a specific backup, use the `--latest-chain` option as follows:
 
 [source,shell]
 ----
-bin/neo4j-admin backup inspect /backups/london-2024-10-07T16-04-05.backup  --show-metadata --latest-chain
+bin/neo4j-admin backup inspect /backups/london-2024-10-07T16-04-05.backup --latest-chain
 ----
 
 .Example output
@@ -229,6 +253,12 @@ bin/neo4j-admin backup inspect /backups/london-2024-10-07T16-04-05.backup  --sho
 In this case, the `--database` option is unnecessary because the database identifier is part of the metadata stored in the header of the backup file _london-2024-10-07T16-04-05.backup_.
 ====
 
+[NOTE]
+====
+Starting with Neo4j 2025.07, the backup metadata is always shown by default when using the `neo4j-admin backup inspect` command.
+If you are on a previous version of Neo4j, you must specify the `--show-metadata` option to see the backup metadata.
+====
+
 
 
 

modules/ROOT/pages/configuration/command-expansion.adoc

@@ -41,14 +41,31 @@ Scripts and their syntax differ between operating systems.
 
 == Enabling
 
-The Neo4j startup script and the `neo4j` service can expand and execute the external commands by using the argument `--expand-commands`.
+To enable command expansion, you must add the `--expand-commands` argument to the Neo4j startup script or _neo4j.service_ file.
+
+=== Starting Neo4j with command expansion
+
+To start Neo4j with command expansion enabled, you can use the following command:
 
 [source, shell]
 ----
 bin/neo4j start --expand-commands
 ----
 
-If the startup script does not receive the `--expand-commands` argument, commands in the configuration file are treated as invalid settings.
+=== Enabling command expansion in Neo4j as a service
+
+If you are using Neo4j as a service, you can enable command expansion by adding the `--expand-commands` argument to the _/etc/systemd/system/neo4j.service_  file.
+Otherwise, the commands in the configuration file are treated as invalid settings.
+
+You must also add `Type=forking` under the `[Service]` section of _/etc/systemd/system/neo4j.service_ to allow for the command expansion.
+
+[source]
+----
+[Service]
+Type=forking
+----
+
+=== Security checks
 
 Neo4j performs the following basic security checks on the _neo4j.conf_ file.
 If they fail, Neo4j does not evaluate the script commands in _neo4j.conf_, and the Neo4j process does not start.

modules/ROOT/pages/configuration/configuration-settings.adoc

@@ -184,6 +184,22 @@ a|An integer.
 m|+++600+++
 |===
 
+
+[role=label--new-2025.07 label--dynamic]
+[[config_db.checkpoint.throughput.limit]]
+=== `db.checkpoint.throughput.limit`
+
+.db.checkpoint.throughput.limit
+[frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
+|===
+|Description
+a|Limit the write throughput per second of the background checkpoint process. This setting is advisory. It is ignored in Neo4j Community Edition and is followed to best effort in Enterprise Edition. Limiting the write IO in this way leaves more bandwidth in the IO subsystem to service random-read IOs, which is important for the response time of queries when the database cannot fit entirely in memory. The only drawback of this setting is that longer checkpoint times may lead to slightly longer recovery times in case of a database or system crash. A lower number means lower IO pressure and, consequently, longer checkpoint times. Set this to null to disable the throughput limit and fallback to IOPS limit.
+|Valid values
+a|A byte size (valid multipliers are B, KiB, KB, K, kB, kb, k, MiB, MB, M, mB, mb, m, GiB, GB, G, gB, gb, g, TiB, TB, PiB, PB, EiB, EB) that is minimum 8.00KiB.
+|Default value
+m|++++++
+|===
+
 == Cloud storage integration settings
 
 Cloud integration settings allow you to specify custom Azure blob storage endpoints and host authorities, set the project ID for Google Cloud Storage buckets, and define the desired throughput for transfer operations in Amazon S3.
@@ -1825,7 +1841,7 @@ For more information, see xref:/performance/statistics-execution-plans.adoc[Stat
 |Description
 a|The default language of a database determines which language is used to evaluate queries that do not explicitly select a language. This setting determines the default language used for new (and initial) databases where not specified as part of `CREATE` or `ALTER` database.
 |Valid values
-a|One of [CYPHER_5, CYPHER_25] that the [] values acceptance depend on 'internal.dbms.cypher.enable_experimental_versions'.
+a|One of [CYPHER_5, CYPHER_25]. label:changed[Changed in 2025.07]
 |Default value
 m|+++CYPHER_5+++
 |===

modules/ROOT/pages/configuration/dynamic-settings.adoc

@@ -36,6 +36,7 @@ RETURN name
 | name                                                           |
 +----------------------------------------------------------------+
 | "db.checkpoint.iops.limit"                                     |
+| "db.checkpoint.throughput.limit"                               |
 | "db.format"                                                    |
 | "db.lock.acquisition.timeout"                                  |
 | "db.logs.query.annotation_data_format"                         |

modules/ROOT/pages/database-internals/checkpointing.adoc

@@ -115,42 +115,42 @@ The following details the expected messages to appear in the _logs\debug.log_ up
 +
 ....
 2023-05-28 12:55:05.174+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for time threshold" @ txId: 49 checkpoint started...
-2023-05-28 12:55:05.253+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for time threshold" @ txId: 49 checkpoint completed in 79ms
+2023-05-28 12:55:05.253+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for time threshold" @ txId: 49 checkpoint completed in 79ms. Checkpoint flushed 74 pages (7% of total available pages), in 58 IOs. Checkpoint performed with IO limit: 789 IOPS, paused in total 0 times(0 millis). Average checkpoint flush speed: 592.0KiB/s.
 ....
 
 * Checkpoint based upon `db.checkpoint.interval.tx`:
 +
 ....
 2023-05-28 13:08:51.603+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for tx count threshold" @ txId: 118 checkpoint started...
-2023-05-28 13:08:51.669+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for tx count threshold" @ txId: 118 checkpoint completed in 66ms
+2023-05-28 13:08:51.669+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for tx count threshold" @ txId: 118 checkpoint completed in 66ms. Checkpoint flushed 74 pages (7% of total available pages), in 58 IOs. Checkpoint performed with IO limit: 789 IOPS, paused in total 0 times(0 millis). Average checkpoint flush speed: 592.0KiB/s.
 ....
 
 * Checkpoint when `db.checkpoint=continuous`:
 +
 ....
 2023-05-28 13:17:21.927+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for continuous threshold" @ txId: 171 checkpoint started...
-2023-05-28 13:17:21.941+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for continuous threshold" @ txId: 171 checkpoint completed in 13ms
+2023-05-28 13:17:21.941+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Scheduled checkpoint for continuous threshold" @ txId: 171 checkpoint completed in 13ms. Checkpoint flushed 74 pages (7% of total available pages), in 58 IOs. Checkpoint performed with IO limit: 789 IOPS, paused in total 0 times(0 millis). Average checkpoint flush speed: 592.0KiB/s.
 ....
 
 * Checkpoint as a result of database shutdown:
 +
 ....
 2023-05-28 12:35:56.272+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Database shutdown" @ txId: 47 checkpoint started...
-2023-05-28 12:35:56.306+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Database shutdown" @ txId: 47 checkpoint completed in 34ms
+2023-05-28 12:35:56.306+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Database shutdown" @ txId: 47 checkpoint completed in 34ms. Checkpoint flushed 74 pages (7% of total available pages), in 58 IOs. Checkpoint performed with IO limit: 789 IOPS, paused in total 0 times(0 millis). Average checkpoint flush speed: 592.0KiB/s.
 ....
 
 * Checkpoint as a result of `CALL db.checkpoint()`:
 +
 ....
 2023-05-28 12:31:56.463+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Call to db.checkpoint() procedure" @ txId: 47 checkpoint started...
-2023-05-28 12:31:56.490+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Call to db.checkpoint() procedure" @ txId: 47 checkpoint completed in 27ms
+2023-05-28 12:31:56.490+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Call to db.checkpoint() procedure" @ txId: 47 checkpoint completed in 27ms. Checkpoint flushed 74 pages (7% of total available pages), in 58 IOs. Checkpoint performed with IO limit: 789 IOPS, paused in total 0 times(0 millis). Average checkpoint flush speed: 592.0KiB/s.
 ....
 
 * Checkpoint as a result of a backup run:
 +
 ....
 2023-05-28 12:33:30.489+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Full backup" @ txId: 47 checkpoint started...
-2023-05-28 12:33:30.509+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Full backup" @ txId: 47 checkpoint completed in 20ms
+2023-05-28 12:33:30.509+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Full backup" @ txId: 47 checkpoint completed in 20ms. Checkpoint flushed 74 pages (7% of total available pages), in 58 IOs. Checkpoint performed with IO limit: 789 IOPS, paused in total 0 times(0 millis). Average checkpoint flush speed: 592.0KiB/s.
 ....
 
 https://neo4j.com/docs/operations-manual/current/monitoring/metrics/reference/#metrics-general-purpose[Checkpoint Metrics] are also available and are detailed in the following files, in the _metrics/_ directory:

modules/ROOT/pages/import.adoc

@@ -1136,6 +1136,7 @@ For example, you can use `uuid:ID(Person){label:Person}`, where the relationship
 * For examples of creating property uniqueness constraints, see link:{neo4j-docs-base-uri}/cypher-manual/current/constraints/managing-constraints/#create-property-uniqueness-constraints[Cypher Manual -> Create property uniqueness constraints].
 ====
 
+[role=label--new-2025.04]
 === Extended header support for Parquet
 
 In addition to the header format supported by the CSV import, the Parquet import supports name-mapping header files.
@@ -1462,8 +1463,9 @@ Now use the previously defined ID spaces when connecting the actors to movies.
 [[import-tool-multiple-ids]]
 == Using multiple node IDs
 
-A node header can also contain multiple `ID` columns, where the relationship data references the composite value of all those columns.
-This also implies using `string` as `id-type`.
+A node header can contain multiple `ID` columns.
+The relationship data must then use a matching number of `START_ID` / `END_ID` columns as references to the composite value of those ID columns.
+This implies using `string` as `id-type`.
 
 For each `ID` column, you can specify to store its values as different node properties.
 However, the composite value cannot be stored as a node property.
@@ -1498,13 +1500,13 @@ Now use both IDs when defining the relationship:
 .relationships_header.csv
 [source, csv]
 ----
-:START_ID,:TYPE,:END_ID
+:START_ID,:START_ID,:TYPE,:END_ID,:END_ID
 ----
 
 .relationships.csv
 [source, csv]
 ----
-aa11,WORKS_WITH,bb22
+aa,11,WORKS_WITH,bb,22
 ----
 ====
 
@@ -1532,13 +1534,13 @@ Now use the defined ID space when connecting John with Paul, and use both IDs in
 .relationships_header.csv
 [source, csv]
 ----
-:START_ID(MyGroup),:TYPE,:END_ID(MyGroup)
+:START_ID(MyGroup),:START_ID(MyGroup),:TYPE,:END_ID(MyGroup),:END_ID(MyGroup)
 ----
 
 .relationships.csv
 [source, csv]
 ----
-aa11,WORKS_WITH,bb22
+aa,11,WORKS_WITH,bb,22
 ----
 ====