Implement a logic to reset an individual stream

[subodh1810]

Epic

• [EPIC] Per-Stream State #6912

Description

As part of this issue we need to build a way to reset the data for an individual stream.

New Requirements:

• Wipe out the entire state for a connector.
• Wipe out the state for individual streams.
• Wipe out the data for individual streams.
• Wipe out all data for a connector.
  • We can tolerate some misses here. e.g. if we try to wipe out the data but the current schema doesn't contain all streams because the schema evolved, it is okay if those streams not in the catalog are not wiped out.

The requirements and implementation for this issue are laid out in this section of the spec.

[cgardens]

@annalvova05 @lmossman @benmoriceau @gosusnp - I have updated this issue to clarify some of the questions that came up in grooming today.

[danieldiamond]

@evantahler is this complete? Does this mean self-hosted airbyte instances are able to reset individual streams within a connector now?

[evantahler]

Almost!

We are soon going to release a version of the Airbyte platform & Airbyte protocol which supports per-stream state. From there, we'll be updating our source connectors to emit state messages per-stream, and destinations that can interpret those per-stream state messages. As connectors are upgraded, yes, Airbyte will be able rest individual streams!

Some foundational work in the UI, for example can be seen in #14634

We will have more to share about this in the near future!