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

Allow sub range for purge_ttl for more shard-friendly columns #713

Closed
jrconlin opened this issue Jul 6, 2020 · 0 comments · Fixed by #718
Closed

Allow sub range for purge_ttl for more shard-friendly columns #713

jrconlin opened this issue Jul 6, 2020 · 0 comments · Fixed by #718
Assignees
Labels
1 Estimate - xs - This is a trivial change with clearly defined parameters.

Comments

@jrconlin
Copy link
Member

jrconlin commented Jul 6, 2020

limit selection for fxa_uid to first n characters.

@jrconlin jrconlin added the 1 Estimate - xs - This is a trivial change with clearly defined parameters. label Jul 6, 2020
@jrconlin jrconlin self-assigned this Jul 6, 2020
@jrconlin jrconlin added this to Backlog: Misc in Services Engineering via automation Jul 6, 2020
@jrconlin jrconlin moved this from Backlog: Misc to In Progress in Services Engineering Jul 6, 2020
@jrconlin jrconlin moved this from In Progress to In Review in Services Engineering Jul 7, 2020
jrconlin added a commit that referenced this issue Jul 7, 2020
Added `--uid_starts` option which will limit purge_ttl bso deletes to
fxa_uids that begin with specified characters.
(e.g.

`purge_ttl.py --uid_starts="AA" --collection_ids=[7,8]`

will limit to scanning bso tables to fxa_uid values that begin with "AA"
and only the 7 & 8 collections

Closes #713
Services Engineering automation moved this from In Review to Done Jul 14, 2020
@tublitzed tublitzed moved this from Done to Archived in Services Engineering Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 Estimate - xs - This is a trivial change with clearly defined parameters.
Projects
Development

Successfully merging a pull request may close this issue.

1 participant