You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### TL;DR
Added a new configuration option for the committer to specify the starting block.
### What changed?
- Introduced a new `fromBlock` parameter for the committer in the configuration.
- Updated the README to document the new `committer-from-block` option.
- Added a new command-line flag `--committer-from-block` with a default value of 0.
- Modified the `CommitterConfig` struct to include the `FromBlock` field.
- Updated the `NewCommitter` function to use the new `FromBlock` value from the committer config instead of the poller config.
### How to test?
1. Run the application with the new `--committer-from-block` flag:
```
./app --committer-from-block 20000000
```
2. Alternatively, set the `COMMITTER_FROMBLOCK` environment variable:
```
export COMMITTER_FROMBLOCK=20000000
./app
```
3. Or update the YAML configuration file:
```yaml
committer:
fromBlock: 20000000
```
4. Verify that the committer starts processing blocks from the specified block number.
### Why make this change?
This change allows users to specify a custom starting block for the committer, providing more flexibility in data processing. It's particularly useful for scenarios where users want to start committing from a specific block height, rather than always starting from the genesis block or the current latest block.
0 commit comments