Repository navigation
Make local tracker use partition key for writing data #319
Description
Context:
This is only an issue if you're using the local tracker as a persister to load from.
Behavior:
If you use the local tracker as a persister, and keep the same app_id, but change the partition key, it'll load from the first instance of app_id if you're loading from prior state.
Task:
- Push through the partition key wherever it makes sense in the local tracker.
- Adjust the server to read from the new location / know how to read old and new locations.
Activity
andreahlert commentedon Mar 28, 2026
Labels migrated to new taxonomy (#692).
HuitaePark commentedon Aug 31, 2026
I noticed that #330 was closed with a note saying the partition-key fix landed in #682. However, #682 appears to address the partition key stored in fork/spawn child pointers (#518), while the current LocalTrackingClient.load() and LocalBackend still use <project>/<app_id> paths and contain TODOs for partition-aware paths.
Is #319 still intended to track making the local storage layout partition-aware? If so, I'd be interested in working on it.