AWS aurora-dsql documentation change
Summary
Updated documentation for asynchronous index creation processes, including command changes (sys.cancel_job to DROP INDEX), removed preview-related notes about concurrency errors, and modified index type references from remote_btree_index to btree_index
Security assessment
Changes appear to be documentation clarifications and command syntax updates rather than security fixes. The removal of a note about concurrency control errors during Preview does not indicate resolution of a security vulnerability. The change from sys.cancel_job to DROP INDEX suggests command correction rather than security mitigation. No explicit security vulnerabilities or security feature additions are mentioned.
Diff
diff --git a/aurora-dsql/latest/userguide/working-with-create-index-async.md b/aurora-dsql/latest/userguide/working-with-create-index-async.md index a51c6a638..dd0b89a7c 100644 --- a//aurora-dsql/latest/userguide/working-with-create-index-async.md +++ b//aurora-dsql/latest/userguide/working-with-create-index-async.md @@ -15 +15 @@ Aurora DSQL immediately returns a `job_id` when you run this command. You can se -Aurora DSQL supports the following job-related procedures: +You can use the following procedures and commands when the index creation job is in progress: @@ -20 +20 @@ Aurora DSQL supports the following job-related procedures: -Block the session until the specified job completes or fails. This procedure returns a Boolean. +Block the session until the specified job completes or fails. This procedure returns a Boolean. @@ -22 +22 @@ Block the session until the specified job completes or fails. This procedure re -`sys.cancel_job` +`DROP INDEX` @@ -25 +25 @@ Block the session until the specified job completes or fails. This procedure re -Cancel an asynchronous job that is in progress. +Cancel an index build job that is in progress. @@ -29,4 +28,0 @@ When Aurora DSQL finishes an asynchronous index task, it updates the system cata -###### Note - -During Preview, asynchronous task completion might result in concurrency control errors for all in-progress transactions that reference the same namespace. - @@ -85,3 +81 @@ Consider the following guidelines: - * During schema migration operations, the `sys.wait_for_job(job_id)` procedure is especially helpful. It ensures that subsequent DDL and DML operations target the newly created index. - - * Every time Aurora DSQL runs a new asynchronous task, it checks the `sys.jobs` view and deletes tasks that have a status of `completed`, `failed`, or `cancelled` for more than 30 minutes. Thus, `sys.jobs` primarily shows in-progress tasks and doesn’t contain information about old tasks. + * During schema migration operations, the `sys.wait_for_job(job_id)` procedure is useful. It ensures that subsequent DDL and DML operations target the newly created index. @@ -89 +83 @@ Consider the following guidelines: - * If you cancel a task, Aurora DSQL automatically updates the corresponding entry in the `sys.jobs` system view. As Aurora DSQL runs the task, it checks the `sys.jobs` view to see if the task has been canceled. If so, Aurora DSQL stops the task. If you encounter an error that Aurora DSQL is updating your schema with another transaction, try to cancel again. After you cancel a task to create an async index, we recommend that you also drop the index. + * Every time Aurora DSQL runs a new asynchronous task, it checks the `sys.jobs` view and deletes tasks that have a status of `completed` or `failed` for more than 30 minutes. Thus, `sys.jobs` primarily shows in-progress tasks and doesn’t contain information about old tasks. @@ -122 +116 @@ The `CREATE INDEX` command returns a job ID, as shown below. -The `job_id` indicates that Aurora DSQL has submitted a new job to create the index. You can use the procedure `sys.wait_for_job(job_id)` to block other work on the session until the job finishes, is canceled, or times out. To cancel an active job, use the procedure `sys.cancel_job(job_id)`. +The `job_id` indicates that Aurora DSQL has submitted a new job to create the index. You can use the procedure `sys.wait_for_job(job_id)` to block other work on the session until the job finishes or times out. @@ -140 +133,0 @@ Aurora DSQL returns a response similar to the following. - yzke2pz3xnhsvol4a3jkmotehq | cancelled | @@ -165,5 +157,0 @@ Aurora DSQL -`cancelled` - - -The task is canceled. - @@ -180,2 +168,2 @@ You can also query the state of the index via the catalog tables `pg_index`and ` - department_pkey | t | CREATE UNIQUE INDEX department_pkey ON test.departments USING remote_btree_index (title) INCLUDE (name, manager, size) - test_index1 | t | CREATE INDEX test_index1 ON test.departments USING remote_btree_index (name, manager, size) + department_pkey | t | CREATE UNIQUE INDEX department_pkey ON test.departments USING btree_index (title) INCLUDE (name, manager, size) + test_index1 | t | CREATE INDEX test_index1 ON test.departments USING btree_index (name, manager, size) @@ -194,2 +182,2 @@ You can query the state of the index using the catalog tables `pg_index`and `pg_ - department_pkey | t | CREATE UNIQUE INDEX department_pkey ON test.departments USING remote_btree_index (title) INCLUDE (name, manager, size) - test_index1 | t | CREATE INDEX test_index1 ON test.departments USING remote_btree_index (name, manager, size) + department_pkey | t | CREATE UNIQUE INDEX department_pkey ON test.departments USING btree_index (title) INCLUDE (name, manager, size) + test_index1 | t | CREATE INDEX test_index1 ON test.departments USING btree_index (name, manager, size) @@ -209,2 +197,2 @@ The `indisunique` flag indicates that the index is `UNIQUE`. To know whether you - department_pkey | t | CREATE UNIQUE INDEX department_pkey ON test.departments USING remote_btree_index (title) INCLUDE (name, manager, size) - test_index1 | f | CREATE INDEX test_index1 ON test.departments USING remote_btree_index (name, manager, size) + department_pkey | t | CREATE UNIQUE INDEX department_pkey ON test.departments USING btree_index (title) INCLUDE (name, manager, size) + test_index1 | f | CREATE INDEX test_index1 ON test.departments USING btree_index (name, manager, size)