-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC-2092] add doc for blocking operation in RO #80
base: main
Are you sure you want to change the base?
Conversation
operation in RO
@@ -24,6 +24,24 @@ Read-only workspaces provide improved performance and scalability for read opera | |||
Current RO workspace requires manual sync up with the RW workspace to catch up with the latest change. | |||
==== | |||
|
|||
=== Block write operations in RO cluster | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we change to RO Workspace? that make sure the description consistent
@@ -22,6 +22,22 @@ Read-only workspaces provide improved performance and scalability for read opera | |||
[NOTE] | |||
==== | |||
Current RO workspace requires manual sync up with the RW workspace to catch up with the latest change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current RO workspace requires manual sync up with the RW workspace to catch up with the latest change. | |
Current Read-Only (RO) workspace requires manual sync up with the RW workspace to catch up with the latest change. |
@@ -22,6 +22,22 @@ Read-only workspaces provide improved performance and scalability for read opera | |||
[NOTE] | |||
==== | |||
Current RO workspace requires manual sync up with the RW workspace to catch up with the latest change. | |||
|
|||
In RO workspace, the following operations are forbidden: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In RO workspace, the following operations are forbidden: | |
In a Read-Only (RO) workspace within TigerGraph Cloud, the following operations are strictly prohibited: |
|
||
In RO workspace, the following operations are forbidden: | ||
|
||
1. run write queries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make the forbidden operations in categories:
Database Operations,
System Administration Commands,
Schema Management,
Graph Management,
Data Modification,
Loading Jobs
Backup and Restore,
address comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zhihuapengtg can you also capitalize each point, and make them easy for end users to understand, here is what is generated by ChatGPT:
Running any queries that modify the database state.
Creating or dropping graphs.
Updating schemas, including adding, updating, or dropping schema elements.
Creating, dropping, or running schema change jobs.
Inserting, updating, or deleting data.
Performing backup or restore operations.
Exporting or importing data.
Executing the DROP ALL command.
Clearing the graph store.
Rebuilding Operations
Rebuilding any part of the database.
Running gadmin or gsql reset commands.
Creating, deleting, or running loading jobs.
Creating or updating data sources.
Creating, deleting, pausing, restarting, or resuming connectors.
ok, thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
❌ Deploy Preview for thriving-strudel-91d4a9 failed.
|
add doc for blocking operation in RO