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
Update Kafka loader guide with new options and Docker example
- Add --reorg-topic, --start-block=latest, --state-dir, --auth options
- Update reorg message format with last_valid_hash field
- Add working Docker example with auth and volume mounts
|`--start-block N`| Latest block | Start streaming from this block |
58
+
|`--start-block N`| Resume from state | Block number or `latest` to start from |
59
+
|`--reorg-topic NAME`| Same as `--topic`| Separate topic for reorg messages |
59
60
|`--label-csv PATH`| - | CSV file for data enrichment |
61
+
|`--state-dir PATH`|`.amp_state`| Directory for LMDB state storage |
62
+
|`--auth`| - | Enable auth using `~/.amp/cache` or `AMP_AUTH_TOKEN` env var |
63
+
|`--auth-token TOKEN`| - | Explicit auth token |
60
64
61
65
## Message Format
62
66
@@ -81,13 +85,14 @@ On blockchain reorganizations, reorg events are sent:
81
85
```json
82
86
{
83
87
"_type": "reorg",
84
-
"network": "ethereum",
88
+
"network": "ethereum-mainnet",
85
89
"start_block": 19000100,
86
-
"end_block": 19000110
90
+
"end_block": 19000110,
91
+
"last_valid_hash": "0xabc123..."
87
92
}
88
93
```
89
94
90
-
Consumers should invalidate data in the specified block range.
95
+
Consumers should invalidate data in the specified block range. Use `--reorg-topic` to send these to a separate topic (useful for Snowflake Kafka connector which requires strict schema per topic).
0 commit comments