update to processor v2 repo (#905)

### Description

### Checklist
<!-- Read the Nextra Contributor's Guide here: https://aptos.dev/en/developer-platforms/contribute -->

- If any existing pages were renamed or removed:
  - [ ] Were redirects added to [next.config.mjs](../apps/nextra/next.config.mjs)?
  - [ ] Did you update any relative links that pointed to the renamed / removed pages?
- Do all Lints pass?
  - [ ] Have you ran `pnpm fmt`?
  - [ ] Have you ran `pnpm lint`?

Author: rtso

apps/nextra/components/beta-notice/IndexerBetaNotice.tsx

@@ -7,7 +7,7 @@ export function IndexerBetaNotice() {
       currently in beta. Please report any problems you encounter by creating an
       issue in the{" "}
       <a
-        href="https://github.com/aptos-labs/aptos-indexer-processors/issues/new/choose"
+        href="https://github.com/aptos-labs/aptos-indexer-processors-v2/issues/new/choose"
         className="_text-primary-600 _underline _decoration-from-font"
         style={{ textUnderlinePosition: "from-font" }}
       >

apps/nextra/pages/en/build/apis/data-providers.mdx

@@ -16,7 +16,7 @@ Indexer layer on top of this will provide a [GRPC transaction stream](../indexer
 
 On top of this transaction stream, we've built out some product logic tables that can be queried through [GraphQL](../indexer/)
 
-Since the logic to parse out transaction is [public](https://github.com/aptos-labs/aptos-indexer-processors), some vendors have implemented similar parsing logic to create a subset of tables and made them available to query.
+Since the logic to parse out transaction is [public](https://github.com/aptos-labs/aptos-indexer-processors-v2), some vendors have implemented similar parsing logic to create a subset of tables and made them available to query.
 
 ## SQL Tables
 

apps/nextra/pages/en/build/indexer/indexer-api/self-hosted.mdx

@@ -44,7 +44,7 @@ From here you will likely want to change the values of some of these fields. Let
 A single instance of the service only runs a single processor. If you want to run multiple processors, you must run multiple instances of the service. In this case, it is up to you whether to use the same database or not.
 </Callout>
 
-This is the processor you want to run. You can see what processors are available [here](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/processor/src/processors/mod.rs#L23). Some examples:
+This is the processor you want to run. You can see what processors are available [here](https://github.com/aptos-labs/aptos-indexer-processors-v2/tree/main/processor/src/processors). Some examples:
 
 - `coin_processor`
 - `ans_processor`
@@ -72,10 +72,10 @@ Clone the repo:
 
 ```bash filename="Terminal"
 # SSH
-git clone git@github.com:aptos-labs/aptos-indexer-processors.git
+git clone git@github.com:aptos-labs/aptos-indexer-processors-v2.git
 
 # HTTPS
-git clone https://github.com/aptos-labs/aptos-indexer-processors.git
+git clone https://github.com/aptos-labs/aptos-indexer-processors-v2.git
 ```
 
 Navigate to the directory for the service:

apps/nextra/pages/en/build/indexer/indexer-sdk.mdx

@@ -28,4 +28,4 @@ Learn how to use the Indexer SDK through guides and documentation.
 
 
 ## Example Processors 
-As a reference, you can see all Aptos-Hosted processors that comprise the Indexer API [here](https://github.com/aptos-labs/aptos-indexer-processors). 
+As a reference, you can see all Aptos-Hosted processors that comprise the Indexer API [here](https://github.com/aptos-labs/aptos-indexer-processors-v2). 

apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/create-processor.mdx

@@ -37,7 +37,7 @@ For basic cases, you can copy the [`IndexerProcessorConfig` from the `aptos-inde
 It's used by `IndexerProcessorConfig.run()` to map the processor name to the right `ProcessorConfig`. 
 
 You can see a basic example of a `ProcessorConfig` [here](https://github.com/aptos-labs/aptos-indexer-processor-example/blob/main/aptos-indexer-processor-example/src/config/processor_config.rs). 
-An example of a more complex setup that includes multiple processors and configurations is [`aptos-indexer-processors`](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/sdk-processor/src/config/processor_config.rs#L84).
+An example of a more complex setup that includes multiple processors and configurations is [`aptos-indexer-processors`](https://github.com/aptos-labs/aptos-indexer-processors-v2/blob/main/processor/src/config/processor_config.rs#L84).
 
 ## How to create a processor
 Now that you've got the configuration pieces set up, the next step is to create the processor. 
@@ -102,7 +102,7 @@ loop {
 ```
 
 You can see a full example of a processor that indexes raw Aptos events in [`aptos-indexer-processor-example`](https://github.com/aptos-labs/aptos-indexer-processor-example/blob/main/aptos-indexer-processor-example/src/processors/events/events_processor.rs). 
-As a reference, you can also see all of the processors that make up the [Indexer API](../../indexer-api.mdx) in [`aptos-indexer-processors`](https://github.com/aptos-labs/aptos-indexer-processors/tree/main/rust/sdk-processor/src/processors).
+As a reference, you can also see all of the processors that make up the [Indexer API](../../indexer-api.mdx) in [`aptos-indexer-processors`](https://github.com/aptos-labs/aptos-indexer-processors-v2/tree/main/processor/src/processors).
 
 ## How to define `main.rs`
 You may copy the [`main.rs`](https://github.com/aptos-labs/aptos-indexer-processor-example/blob/main/aptos-indexer-processor-example/src/main.rs) file from the `aptos-indexer-processor-example`. 

apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/define-schema.mdx

@@ -17,7 +17,7 @@ By using the indexer, a single indexer query can often replace multiple queries
 ## Aptos Core Processors
 All data exposed by the [Indexer API](../../indexer-api.mdx) is initially indexed using custom processors.
 Each core processor indexes a specific type of data.
-You can explore the [full list of processors](https://github.com/aptos-labs/aptos-indexer-processors/tree/main/rust/sdk-processor/src/processors) and the [complete indexer data schema](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/processor/src/db/postgres/schema.rs).
+You can explore the [full list of processors](https://github.com/aptos-labs/aptos-indexer-processors-v2/blob/main/processor/src/db/schema.rs).
 
 The Aptos core processors and the [Quickstart Guide](../quickstart.mdx) use [PostgreSQL](https://www.postgresql.org/) as the database and [Diesel](https://diesel.rs/) as the ORM.
 If you'd also like to use PostgreSQL and Diesel, you can follow the instructions in [PostgreSQL Installation](../quickstart.mdx#postgresql-installation).

apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/version-tracking.mdx

@@ -5,7 +5,7 @@ title: "Version Tracking"
 # Version Tracking, Restart Behavior, and Backfilling
 
 ## Version Tracking
-The `VersionTrackerStep` is a [common step in the SDK](https://github.com/aptos-labs/aptos-indexer-processor-sdk/blob/main/aptos-indexer-processors-sdk/sdk/src/common_steps/version_tracker_step.rs#L29C12-L29C30) that checkpoints indexer progress. The struct requires implementation of the [`ProcessorStatusSaver` trait](https://github.com/aptos-labs/aptos-indexer-processor-sdk/blob/main/aptos-indexer-processors-sdk/sdk/src/common_steps/version_tracker_step.rs#L16) and can be used with the same [`.connect_to()`](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/sdk-processor/src/processors/events_processor.rs#L117) method as other steps.  Upon a successfully processed batch, the `VersionTrackerStep` will [call](https://github.com/aptos-labs/aptos-indexer-processor-sdk/blob/main/aptos-indexer-processors-sdk/sdk/src/common_steps/version_tracker_step.rs#L57) the trait implementation of `save_processor_status()`.
+The `VersionTrackerStep` is a [common step in the SDK](https://github.com/aptos-labs/aptos-indexer-processors-v2/blob/main/processor/src/processors/events/events_processor.rs#L125) method as other steps.  Upon a successfully processed batch, the `VersionTrackerStep` will [call](https://github.com/aptos-labs/aptos-indexer-processor-sdk/blob/main/aptos-indexer-processors-sdk/sdk/src/common_steps/version_tracker_step.rs#L57) the trait implementation of `save_processor_status()`.
 
 ### ProcessorStatusSaver
 The `ProcessorStatusSaver` trait requires the implementation of the method `save_processor_status` with the following signature:
@@ -16,11 +16,17 @@ async fn save_processor_status(
         last_success_batch: &TransactionContext<()>,
     ) -> Result<(), ProcessorError>;
 ```
-This method is where checkpointing should be written. Examples can be found [here](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/sdk-processor/src/steps/common/processor_status_saver.rs#L23). It is possible to checkpoint progress in different ways by using enums. [This example](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/sdk-processor/src/steps/common/processor_status_saver.rs#L131) inserts into Postgres using a simple [`processor_status` model](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/processor/src/db/postgres/models/processor_status.rs). 
+This method is where checkpointing should be written. 
+If you're writing to Postgres, you can use the SDK's Postgres implementation [here](https://github.com/aptos-labs/aptos-indexer-processor-sdk/blob/main/aptos-indexer-processors-sdk/sdk/src/postgres/utils/checkpoint.rs#L66). 
+It is possible to checkpoint progress in different ways by using enums. 
+The SDK's Postgres implementation inserts using a simple [`processor_status` model](https://github.com/aptos-labs/aptos-indexer-processor-sdk/blob/main/aptos-indexer-processors-sdk/sdk/src/postgres/models/processor_status.rs). 
 
 
 ## Restart Behavior 
-Now that the processor successfully writes to the chosen store for version tracking, upon restarting it needs to retrieve the latest successful version from that store. [Here is an example](https://github.com/aptos-labs/aptos-indexer-processors/blob/29f4e9c2266db11cbec2177c17fc210d4c687d32/rust/sdk-processor/src/utils/starting_version.rs#L26) of a `get_starting_version()` method that returns the latest processed version saved. This `starting_version: u64` can then be used as below. If there is no checkpoint, the processor will start from the beginning of the chain.
+Now that the processor successfully writes to the chosen store for version tracking, upon restarting it needs to retrieve the latest successful version from that store. 
+[Here is an example](https://github.com/aptos-labs/aptos-indexer-processor-sdk/blob/main/aptos-indexer-processors-sdk/sdk/src/postgres/utils/checkpoint.rs#L118) of a `get_starting_version()` method that returns the latest processed version saved. 
+This `starting_version: u64` can then be used as below. 
+If there is no checkpoint, the processor will start from the beginning of the chain.
 
 ```rust
  let transaction_stream = TransactionStreamStep::new(TransactionStreamConfig {
@@ -32,47 +38,28 @@ Now that the processor successfully writes to the chosen store for version track
 
 
 ## Backfilling
-To enable backfilling, `IndexerProcessorConfig`, `ProcessorStatusSaver` and `get_starting_version()` need some updates. Without these changes, it is difficult to run a live processor at the latest transaction version as well as a backfill processor. 
+The SDK does not provide an implementation of `ProcessorStatusSaver` that will save backfill progress.
+ To enable saving backfill progress, `IndexerProcessorConfig`, `ProcessorStatusSaver` and `get_starting_version()` need some updates.
+Without these changes, it is difficult to run a live processor at the latest transaction version as well as a backfill processor. 
 
 ### Updates to Config
-[Add an additional field](https://github.com/aptos-labs/aptos-indexer-processor-example/blob/main/aptos-indexer-processor-example/src/config/indexer_processor_config.rs#L20) on your `IndexerProcessorConfig` for a `BackfillConfig` which contains a single field, `backfill_alias`. The introduction of this field will be used to determine whether the processor is a backfill processor or regular one.
-
-```rust
-#[derive(Clone, Debug, Deserialize, Serialize)]
-#[serde(deny_unknown_fields)]
-pub struct IndexerProcessorConfig {
-    pub processor_config: ProcessorConfig,
-    pub transaction_stream_config: TransactionStreamConfig,
-    pub db_config: DbConfig,
-    pub backfill_config: Option<BackfillConfig>,
-}
-
-#[derive(Debug, Clone, Serialize, Deserialize)]
-pub struct BackfillConfig {
-    pub backfill_alias: String,
-}
-```
+[Add an additional field](https://github.com/aptos-labs/aptos-indexer-processors-v2/blob/main/processor/src/config/processor_mode.rs#L29) on your `IndexerProcessorConfig` for a `BackfillConfig`.
+In this implementation, the `BackfillConfig` is part of an enum `ProcessorMode` that is used to determine the mode the processor is running in.
+In backfill mode, the processor starts from a different version and the progress is saved in a separate table. 
 
 ### Updates to `config.yaml`
-Add the `backfill_config` section to `server_config` in your yaml file to set `backfill_alias`.
-
-```yaml
-server_config:
-    processor_config:
-        type: "events_processor"
-        ...
-    backfill_config:
-        backfill_alias: "events_processor_backfill"
-```
-
+Add the `backfill_config` section to `server_config` in your yaml file to set `backfill_alias`. [Example](https://github.com/aptos-labs/aptos-indexer-processors-v2/blob/main/processor/example-backfill-config.yaml)
 
 ### Backfill Processor Status Table
-Use a separate table for backfill processor status to avoid write conflicts. This table (`backfill_processor_status_table`) uses `backfill_alias` as the primary key instead of `processor_name` to prevent conflicts with the main `processor_status` table when running head and backfill processors concurrently. Create multiple backfill processors with differing `backfill_alias` and transaction version ranges for a faster backfill.
-Expand on this [implementation](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/sdk-processor/src/db/common/models/backfill_processor_status.rs). This model introduces a new state, `BackfillStatus`, which is either `InProgress` or `Complete` which will determine the backfilling restart behavior.
+Use a separate table for backfill processor status to avoid write conflicts. This table (`backfill_processor_status_table`) uses `backfill_alias` as the primary key instead of `processor_name` to prevent conflicts with the main `processor_status` table when running head and backfill processors concurrently. 
+Create multiple backfill processors with differing `backfill_alias` and transaction version ranges for a faster backfill.
+Expand on this [implementation](https://github.com/aptos-labs/aptos-indexer-processors-v2/blob/main/processor/src/db/backfill_processor_status.rs). 
+This model introduces a new state, `BackfillStatus`, which is either `InProgress` or `Complete` which will determine the backfilling restart behavior.
 
 ### Updates to ProcessorStatusSaver
-Expand your `ProcessorStatusSaverEnum` to include a `Backfill` variant that extracts the `backfill_alias` from the `BackfillConfig`, and the `backfill_start_version` `backfill_end_version` from `IndexerProcessorConfig.transaction_stream_config` [like this](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/sdk-processor/src/steps/common/processor_status_saver.rs#L27). Update the corresponding write query to write to the new `backfill_processor_status` table.
+Expand your `ProcessorStatusSaver` implementation to include a `Backfill` variant that extracts the `backfill_alias` from the `BackfillConfig`, and the `backfill_start_version` `backfill_end_version` from `IndexerProcessorConfig.transaction_stream_config` [like this](https://github.com/aptos-labs/aptos-indexer-processors-v2/blob/main/processor/src/processors/processor_status_saver.rs#L96). 
+Update the corresponding write query to write to the new `backfill_processor_status` table.
 
 ### Updates to get_starting_version
-Add a [statement](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/sdk-processor/src/utils/starting_version.rs#L143) in your `get_starting_version` method to query the `backfill_processor_status_table` when the `BackfillConfig` field is present in `IndexerProcessorConfig` .
+Add a [statement](https://github.com/aptos-labs/aptos-indexer-processors-v2/blob/main/processor/src/processors/processor_status_saver.rs#L190) in your `get_starting_version` method to query the `backfill_processor_status_table` when the `BackfillConfig` field is present in `IndexerProcessorConfig` .