[ASTS] Foreground Task I: The Ramp

[jeremyk-91]

General

Before this PR: While a lot of the primitives exist, we don't actually have a piece that ties them together as part of sweep.

After this PR:

==COMMIT_MSG==
We implement SingleBucketSweepTask, which uses the existing components to sweep a specific bucket.
==COMMIT_MSG==

Priority: P2

Concerns / possible downsides (what feedback would you like?):

• This feels a bit too invasive on the state machine table, should we expose that value somewhere else?
• Testing is a nightmare - it doesn't exist yet, but some will be added - in [ASTS] Foreground Task II: SingleBucketSweepTaskIntegrationTest #7288 and [ASTS] Foreground Task II.B: Add mock-based tests for DefaultSingleBucketSweepTask #7294.

Is documentation needed?: No.

Compatibility

Does this PR create any API breaks (e.g. at the Java or HTTP layers) - if so, do we have compatibility?: No

Does this PR change the persisted format of any data - if so, do we have forward and backward compatibility?: No

The code in this PR may be part of a blue-green deploy. Can upgrades from previous versions safely coexist? (Consider restarts of blue or green nodes.): Yes

Does this PR rely on statements being true about other products at a deployment - if so, do we have correct product dependencies on these products (or other ways of verifying that these statements are true)?: No

Does this PR need a schema migration? No

Testing and Correctness

What, if any, assumptions are made about the current state of the world? If they change over time, how will we find out?: Nothing in particular

What was existing testing like? What have you done to improve it?: This is new code. This PR probably can be reviewed by itself, though actual production usage should only begin after Part III (to be written) merges.

If this PR contains complex concurrent or asynchronous code, is it correct? The onus is on the PR writer to demonstrate this.: N/A

If this PR involves acquiring locks or other shared resources, how do we ensure that these are always released?: N/A

Execution

By itself this is not going to change anything.

SafeArgs question: yeah, checked this is fine.

Scale

Would this PR be expected to pose a risk at scale? Think of the shopping product at our largest stack.: No

Would this PR be expected to perform a large number of database calls, and/or expensive database calls (e.g., row range scans, concurrent CAS)?: No

Would this PR ever, with time and scale, become the wrong thing to do - and if so, how would we know that we need to do something differently?: When we need to rearchitect sweep, maybe.

Development Process

Where should we start reviewing?: the one file

If this PR is in excess of 500 lines excluding versions lock-files, why does it not make sense to split it?: N/A

Please tag any other people who should be aware of this PR:
@jeremyk-91
@sverma30
@raiju

[changelog-app]

Generate changelog in changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

We implement SingleBucketSweepTask, which uses the existing components to sweep a specific bucket.

Check the box to generate changelog(s)

• Generate changelog entry