diff --git a/.github/workflows/ci-spell-checking.yml b/.github/workflows/ci-spell-checking.yml index a85da8f1..6febdca6 100644 --- a/.github/workflows/ci-spell-checking.yml +++ b/.github/workflows/ci-spell-checking.yml @@ -22,7 +22,7 @@ jobs: - uses: actions/checkout@v3 - name: Get changed files in the content folder id: changed-files-specific - uses: tj-actions/changed-files@v35 + uses: tj-actions/changed-files@v41 with: files: ./content/ - name: Install Vale diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml new file mode 100644 index 00000000..b71b891c --- /dev/null +++ b/.github/workflows/stale.yml @@ -0,0 +1,18 @@ +name: 'Close stale issues and PRs' +on: + schedule: + - cron: '30 1 * * *' + +permissions: + issues: write + pull-requests: write + +jobs: + stale: + runs-on: ubuntu-latest + steps: + - uses: actions/stale@v9 + with: + stale-issue-message: 'This issue has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open.' + stale-pr-message: 'This PR has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open.' + operations-per-run: 100 diff --git a/README.md b/README.md index 4131a2c6..170cf810 100644 --- a/README.md +++ b/README.md @@ -106,6 +106,4 @@ Pass custom Go-GRPC example to the runnable by passing a `customExampleGoGRPC` t **Note:** Runnable doesn't support passing a multiline string as an argument to a shortcode. Therefore, you have to create the whole custom example in a single line string by replacing newlines with `\n`. ## History -v24.0: -======= add Hypermode banner by updating the hugo-docs repository with topbat template. diff --git a/content/deploy/admin/metrics.md b/content/deploy/admin/metrics.md index a4e1d12c..665b7f5a 100644 --- a/content/deploy/admin/metrics.md +++ b/content/deploy/admin/metrics.md @@ -36,6 +36,28 @@ not interact directly with the filesystem. Instead it relies on Metric | Description ------- | ----------- + `badger_read_num_vlog` | Total count of reads by badger in vlog, + `badger_write_num_vlog` | Total count of writes by Badger in vlog, + `badger_read_bytes_vlog` | Total bytes read by Badger, + `badger_write_bytes_vlog` | Total bytes written by Badger, + `badger_read_bytes_lsm` | Total bytes read by Badger, + `badger_write_bytes_l0` | Total bytes written by Badger, + `badger_write_bytes_compaction` | Total bytes written by Badger, + `badger_get_num_lsm` | Total count of LSM gets, + `badger_get_num_memtable` | Total count of LSM gets from memtable, + `badger_hit_num_lsm_bloom_filter` | Total count of LSM bloom hits, + `badger_get_num_user` | Total count of calls to Badger's `get`, + `badger_put_num_user` | Total count of calls to Badger's `put`, + `badger_write_bytes_user` | Total bytes written by user, + `badger_get_with_result_num_user` | Total count of calls to Badger's `get` that returned value, + `badger_iterator_num_user` | Total count of iterators made in badger, + `badger_size_bytes_lsm` | Size of the LSM in bytes, + `badger_size_bytes_vlog` | Size of the value log in bytes, + `badger_write_pending_num_memtable` | Total count of pending writes, + `badger_compaction_current_num_lsm` | Number of tables being actively compacted, + + Old Metrics (Pre 23.1.0) + `badger_disk_reads_total` | Total count of disk reads in Badger. `badger_disk_writes_total` | Total count of disk writes in Badger. `badger_gets_total` | Total count of calls to Badger's `get`. diff --git a/content/deploy/cli-command-reference.md b/content/deploy/cli-command-reference.md index e60dbe57..6bd99594 100644 --- a/content/deploy/cli-command-reference.md +++ b/content/deploy/cli-command-reference.md @@ -40,8 +40,8 @@ The general syntax for superflags is as follows: `-- option-a=v {{% notice "note" %}} You should encapsulate the options for a superflag in double-quotes (`"`) if any -of those option values include spaces. You can also encapsulate options in -double-quotes to improve readability. So, you can also use the following +of those option values include spaces. You can encapsulate options in +double-quotes to improve readability. You can also use the following syntax for superflags: `-- "option-a=value; option-b=value"`. {{% /notice %}} @@ -229,7 +229,7 @@ The commands in these groups are shown in the following table: | Dgraph debug | [`debuginfo`](#dgraph-debuginfo) | Generates information about the current node for use in debugging issues with Dgraph clusters | | Dgraph tools | [`completion`](#dgraph-completion) | Generates shell completion scripts for `bash` and `zsh` | | Dgraph tools | [`conv`](#dgraph-conv) | Converts geographic files into RDF so that they can be consumed by Dgraph | -| Dgraph tools | [`decrypt`](#dgraph-decrypt) | Decrypts an export file created by an encrypted Dgraph cluster | +| Dgraph tools | [`decrypt`](#dgraph-decrypt) | Decrypts an export file created by an encrypted Dgraph Cluster | | Dgraph tools | [`export_backup`](#dgraph-export_backup) | Converts a binary backup created using Dgraph Enterprise Edition into an exported folder. | | Dgraph tools | [`increment`](#dgraph-increment) | Increments a counter transactionally to confirm that a Dgraph Alpha node can handle query and mutation requests | | Dgraph tools | [`lsbackup`](#dgraph-lsbackup) | Lists information on backups in a given location | @@ -929,7 +929,7 @@ Use "dgraph conv [command] --help" for more information about a command. #### `dgraph decrypt` This command lets you decrypt an export file created by an encrypted Dgraph -cluster. The following replicates the help listing shown when you run +Cluster. The following replicates the help listing shown when you run `dgraph decrypt --help`: ```shell @@ -1080,33 +1080,6 @@ Flags: Use "dgraph migrate [command] --help" for more information about a command. ``` -#### `dgraph raftmigrate` - -This command runs the Dgraph Raft migration tool. -The following replicates the help listing shown when you run `dgraph raftmigrate --help`: - -```shell -Run the Raft migration tool -Usage: - dgraph raftmigrate [flags] - -Flags: - --encryption_key_file string The file that stores the symmetric key of length 16, 24, or 32 bytes. The key size determines the chosen AES cipher (AES-128, AES-192, and AES-256 respectively). Enterprise feature. - -h, --help help for raftmigrate - --new-dir string Path to the new (z)w directory. - --old-dir string Path to the old (z)w directory. - --vault string Vault options - addr=http://localhost:8200; Vault server address in the form of http://ip:port - field=enc_key; Vault kv store field whose value is the base64 encoded encryption key. - format=base64; Vault field format: raw or base64. - path=secret/data/dgraph; Vault kv store path. e.g. secret/data/dgraph for kv-v2, kv/dgraph for kv-v1. - role-id-file=; File containing Vault role-id used for approle auth. - secret-id-file=; File containing Vault secret-id used for approle auth. - (default "addr=http://localhost:8200; path=secret/data/dgraph; field=enc_key; format=base64; role-id-file=; secret-id-file=;") - -Use "dgraph raftmigrate [command] --help" for more information about a command. -``` - #### `dgraph upgrade` This command helps you to upgrade from an earlier Dgraph release to a newer release. diff --git a/content/dql/dql-get-started.md b/content/dql/dql-get-started.md index 90f9f031..9216facb 100644 --- a/content/dql/dql-get-started.md +++ b/content/dql/dql-get-started.md @@ -135,7 +135,7 @@ Alter the schema to add indexes on some of the data so queries can use term matc Set the index for the `release_date`: 1. Select `release_date` predicate. -2. Change the type to **date** +2. Change the type to **datetime** 3. Select **index** and choose **year** for the index type. 4. Click **Update** to apply the index on the `release-date` predicate. diff --git a/content/enterprise-features/binary-backups.md b/content/enterprise-features/binary-backups.md index 44fc0999..70c5eae3 100644 --- a/content/enterprise-features/binary-backups.md +++ b/content/enterprise-features/binary-backups.md @@ -693,7 +693,7 @@ input RestoreTenantInput { } ``` -## Offline restore +## Offline restore (DEPRECATED) The restore utility is now a standalone tool. A new flag, `--encryption key-file=value`, is now part of the restore utility, so you can use it to decrypt the backup. The file specified using this flag must contain the same key that was used for encryption during backup. Alternatively, starting with `v20.07.0`, the `vault` superflag can be used to restore a backup. diff --git a/content/graphql/schema/directives/ids.md b/content/graphql/schema/directives/ids.md index 0ac19ffb..aeeeb13d 100644 --- a/content/graphql/schema/directives/ids.md +++ b/content/graphql/schema/directives/ids.md @@ -89,8 +89,7 @@ In the above example, `itemID` won't be present as an argument to the `getItem` `get` queries generated for an interface will have only the `@id(interface: true)` fields as arguments. {{% /notice %}} - -### Combining `ID` and `@id` +## Combining `ID` and `@id` You can use both the `ID` type and the `@id` directive on another field definition to have both a unique identifier and a generated identifier. @@ -110,7 +109,7 @@ With this schema, Dgraph requires a unique `username` when creating a new user. If in a type there are multiple `@id` fields, then in a `get` query these arguments will be optional. If in a type there's only one field defined with either `@id` or `ID`, then that will be a required field in the `get` query's arguments. {{% /notice %}} -