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
Copy file name to clipboardExpand all lines: docs/dynamodb.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
PartForge tracks every part of every job as a row in a single DynamoDB table. This is the source of truth for the pipeline: workers claim work with conditional updates, transition parts through their lifecycle, and record progress and compaction lineage here. Because all state lives in DynamoDB, jobs are resumable and can be driven by many workers at once.
4
4
5
5
The table holds no bulk data — only per-part metadata and pointers to the S3 artifacts. Part data itself lives in S3.
6
-
Rows may include `job_name` when `upload-freeze -job-name` is used; `list-jobs` displays it with the job ID.
6
+
Rows may include `job_name` when `upload-freeze -job-name` is used; `list-jobs` displays it with job status, counts, and timestamps.
Copy file name to clipboardExpand all lines: docs/operations.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,11 +34,11 @@ Workers also write a per-part progress heartbeat to DynamoDB every `15s` (`-stat
34
34
## Inspecting jobs
35
35
36
36
```sh
37
-
partforge list-jobs #job IDs and optional names in the state table (uses the gsi1 index)
37
+
partforge list-jobs #jobs with status, part counts, submitted/updated timestamps, optional names (uses the gsi1 index)
38
38
partforge job-status -job-id=job-123
39
39
```
40
40
41
-
Both accept `-json`; `list-jobs -json` keeps `jobs` as job IDs and adds `job_names` when names are set. `job-status -parts` adds per-row detail (persisted rewrite counters, compact-ready age, destination partitions, active part stats, `FAILED_MERGES`); `job-status -details` adds each part's current stage and per-stage timings. The physical part counters (`input_clickhouse_parts`, `current_output_clickhouse_parts`) refer to ClickHouse parts, not state rows.
41
+
Both accept `-json`; `list-jobs -json` keeps `jobs` as job IDs, adds `job_names` when names are set, and includes `job_details` for status/progress/timestamps. `job-status -parts` adds per-row detail (persisted rewrite counters, compact-ready age, destination partitions, active part stats, `FAILED_MERGES`); `job-status -details` adds each part's current stage and per-stage timings. The physical part counters (`input_clickhouse_parts`, `current_output_clickhouse_parts`) refer to ClickHouse parts, not state rows.
0 commit comments