Skip to content
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

spanconfig: harden infrastructure for v22.1 #73874

Closed
17 of 24 tasks
irfansharif opened this issue Dec 15, 2021 · 4 comments
Closed
17 of 24 tasks

spanconfig: harden infrastructure for v22.1 #73874

irfansharif opened this issue Dec 15, 2021 · 4 comments
Assignees
Labels
A-zone-configs C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) E-quick-win Likely to be a quick win for someone experienced. T-kv KV Team

Comments

@irfansharif
Copy link
Contributor

irfansharif commented Dec 15, 2021

#67679 wrapped up the major feature work for span configs (rfc: #66348). This issue tracks the miscellaneous TODOs/bugs we left along the way; we should try and address them pre-22.1. They're categorized by size+necessity and ordered unscientifically by when we should do them.

Small:

Medium:

Epic CRDB-10563

Jira issue: CRDB-11795

@irfansharif irfansharif added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-zone-configs E-quick-win Likely to be a quick win for someone experienced. labels Dec 15, 2021
@mwang1026 mwang1026 added this to Incoming in KV via automation Dec 15, 2021
@blathers-crl blathers-crl bot added the T-kv KV Team label Dec 15, 2021
@mwang1026 mwang1026 moved this from Incoming to 22.1 Roadmap in KV Dec 15, 2021
@irfansharif irfansharif moved this from 22.1 Roadmap to Quick Wins in KV Dec 15, 2021
@irfansharif irfansharif moved this from Quick Wins to Current Milestone in KV Dec 15, 2021
@irfansharif irfansharif added this to Triage in (OBSOLETE) Multi-tenant via automation Dec 16, 2021
@ajwerner
Copy link
Contributor

@irfansharif can we track #73045 somewhere if not here? It's really in the critical path and I need to know when and how it's getting done.

@irfansharif
Copy link
Contributor Author

Added, this list as good as any to track it.

@irfansharif irfansharif self-assigned this Jan 4, 2022
@ajstorm ajstorm moved this from Triage to In progress in (OBSOLETE) Multi-tenant Jan 19, 2022
@irfansharif
Copy link
Contributor Author

Adding #76608 to the list, something we hadn't thought of in the context of index-backfills.

@irfansharif
Copy link
Contributor Author

This thing is done. There are specific issues or PRs for all the remaining nice-to-haves. Two shorter term things we should probably do:

Multi-tenant zone configs automation moved this from v22.1 to Done Apr 19, 2022
(OBSOLETE) Multi-tenant automation moved this from In progress to Done Apr 19, 2022
KV automation moved this from Current Milestone / In Progress to Closed Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-zone-configs C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) E-quick-win Likely to be a quick win for someone experienced. T-kv KV Team
Projects
KV
Closed
Development

No branches or pull requests

3 participants