backupccl: schedule status, jobs for specific schedule's status, etc. #51850
Assignees
Labels
A-disaster-recovery
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Comments
mwang1026
added
C-enhancement
craig bot
pushed a commit
that referenced
this issue
Aug 3, 2020
51865: sql: use the descs.Collection to access types during distributed flows r=rohany a=rohany This commit enables distributed queries to access user defined type metadata during flow setup via the lease manager, so that accesses to this metadata is cached and doesn't have to go through k/v on every access. This is achieved by giving the `FlowContext` a `descs.Collection` is used to access the descriptors through the lease manager. Release note: None 51939: interval/generic: improve randomized testing, fix upper bound bug r=nvanbenschoten a=nvanbenschoten In an effort to track down the bug that triggered #51913, this commit ports the randomized interval btree benchmarks to also be unit tests. This allows us to run invariant checks (see `btree.Verify`) on randomized tree configurations. Doing so revealed a violation of the `isUpperBoundCorrect` invariant. This was determined to be a bug in `node.removeMax`. When removing an item from a grandchild node, we were failing to adjust the upper bound of the child node. It doesn't look like this could cause user-visible effects because the upper bound of a subtree is only ever decreased on removal, so at worst, this caused searches in the tree to do more work than strictly necessary. Still, this is a good bug to fix and it's encouraging that the new randomized testing using the existing invariant validation caught it. 52090: sql: support ALTER TABLE SET SCHEMA command r=rohany a=RichardJCai sql: support ALTER TABLE SET SCHEMA command Release note (sql change): Added support for ALTER TABLE/SEQUENCE/VIEW SET SCHEMA to set the schema of the table to the target schema. One must have DROP privilege on the table and CREATE privilege on the schema to perform the operation. 52230: bulkio: Implement `SHOW SCHEDULES` r=miretskiy a=miretskiy Informs #51850 Informs #51600 Implement `SHOW SCHEDULES` statemen which displays the information on scheduled jobs. Display schedule information, optionally filtered by schedule state (paused or not) and optionally restricted just to the backup schedules: ``` SHOW [RUNNING|PAUSED] SCHEDULES [FOR BACKUP] ``` In addition, it is possible to display information for a specific schedule: ``` SHOW SCHEDULE 123 ``` Release Notes (enterprise change): `SHOW SCHEDULES` displays information about the scheduled jobs. Co-authored-by: Rohan Yadav <rohany@alumni.cmu.edu> Co-authored-by: Nathan VanBenschoten <nvanbenschoten@gmail.com> Co-authored-by: richardjcai <caioftherichard@gmail.com> Co-authored-by: Yevgeniy Miretskiy <yevgeniy@cockroachlabs.com>
craig bot
pushed a commit
that referenced
this issue
Aug 4, 2020
52274: sql: Add a `FOR SCHEDULES` clause to `SHOW JOBS` r=miretskiy a=miretskiy Informs #51850 Informs #51989 Add a `FOR SCHEDULES` clause to `SHOW JOBS` command to display jobs started by the specified schedules. Release Notes (enterprise change): Add ability to display jobs started by specified schedule. Co-authored-by: Yevgeniy Miretskiy <yevgeniy@cockroachlabs.com>
|
Going to close this issue for now; Future work can be handled w/ future feature requests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A user who sets up a schedule needs to be able to inspect, and debug, the status of the schedule and of the jobs that the schedule kicked off.
** Deliverables **
SHOWtype commands to see schedule status, and of jobs associated with that schedule** Future scope **
The text was updated successfully, but these errors were encountered: