taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

updates

Browse Source 
Signed-off-by: Colin Sullivan <colin@synadia.com>
This commit is contained in:
Colin Sullivan 2021-05-14 15:57:56 -06:00
commit e83040540e
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
jetstream/administration/naming.md
View File

@ -9,13 +9,18 @@ friendly to the file system.
We recommend the following guideline for stream, consumer, and account names: We recommend the following guideline for stream, consumer, and account names:
* Alphanumeric values are recommended. * Alphanumeric values are recommended.
<<<<<<< HEAD
* Spaces, tabs, period \(`.`\), greater than \(`>`\) or asterix \(`*`\) are prohibited. * Spaces, tabs, period \(`.`\), greater than \(`>`\) or asterix \(`*`\) are prohibited.
* Limit name length. The JetStream storage directories will include the account, * Limit name length. The JetStream storage directories will include the account,
stream name, and consumer name, so a generally safe approach would be to keep names stream name, and consumer name, so a generally safe approach would be to keep names
under 32 characters. under 32 characters.
=======
* Spaces, tabs, period \(`.`\), greater than \(`>`\) or asterisk \(`*`\) are prohibited.
* Limit names to 255 characters or less.
>>>>>>> 60f3fbb79fa5c1aa9c6d18b3d45321820e228b77
* Do not use reserved file names like NUL, LPT1, etc. * Do not use reserved file names like NUL, LPT1, etc.
* Be aware that some file systems are case insentitive so do not * Be aware that some file systems are case insentitive so do not
use stream or account names that would collide in a file system. use stream or account names that would collide in a file system.
For example, `Foo` and `foo` would collide on a Windows or Mac OSx System. For example, `Foo` and `foo` would collide on a Windows or Mac OSx System.
We plan to address these limitations in a future release. We plan to address these limitations in a future release.

2
jetstream/concepts/streams.md
View File

@ -16,7 +16,7 @@ When defining Streams the items below make up the entire configuration of the se
| Item | Description | | Item | Description |
| :--- | :--- | | :--- | :--- |
| Name | A name for the Stream that may not have spaces, tabs, period \(`.`\), greater than \(`>`\) or asterix \(`*`\). See [naming](../administration/naming.md] | | Name | A name for the Stream that may not have spaces, tabs, period \(`.`\), greater than \(`>`\) or asterisk \(`*`\). See [naming](../administration/naming.md] |
| Storage | The type of storage backend, `File` and `Memory` | | Storage | The type of storage backend, `File` and `Memory` |
| Subjects | A list of subjects to consume, supports wildcards | | Subjects | A list of subjects to consume, supports wildcards |
| Replicas | How many replicas to keep for each message in a clustered JetStream, maximum 5 | | Replicas | How many replicas to keep for each message in a clustered JetStream, maximum 5 |