feat: implement Firestore event and error storage (Issue #2) #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Implements persistent storage for events and errors using Google Cloud Firestore with batch operations, retry logic, and stream-based isolation.
Closes #2
Implementation Details
FirestoreEventStore
asyncio.to_thread()to wrap sync Firestore clientstore(),store_batch(),read(stream, limit)FirestoreErrorStore (Dead Letter Queue)
errors/collectionstore_error(),query_errors(limit)Testing
Docker Compose
docker-compose.ymlwith Firestore emulatorCommits
store(),store_batch()with tenacity retriesread(),_dict_to_event()with type routingTesting
Files Changed
src/eventkit/stores/firestore.py(new, 240 lines)tests/unit/stores/test_firestore.py(new, 270 lines)tests/integration/test_firestore_integration.py(new, 140 lines)docker-compose.yml(new)pytest.ini(updated with integration marker)README.md(updated with Docker instructions)pyproject.toml(added tenacity dependency)src/eventkit/schema/events.py(added stream field)specs/core-pipeline/tasks.md(marked Task 4 complete)Dependencies Added
tenacity>=8.2.0- Retry logic with exponential backoffAcceptance Criteria (All Met)
{stream}/{timestamp}_{uuid}