Implement watchdog client and automatic file indexing - #14
Closed
Aryan-Ranga wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR implements the first version of the automatic file indexing pipeline using a Watchdog client. The backend now supports real-time synchronisation between the local filesystem and the indexed document database.
Features Implemented
Added a standalone Watchdog client to monitor user-selected folders.
Implemented startup scanning to index existing files in watched folders.
Added automatic handling of:
File creation
File modification (re-indexing)
File deletion
File rename/move
Added REST endpoints for:
Uploading files for background indexing
Deleting files by file path
Renaming tracked file paths
Managing watched folders
Added a WatchedFolder database model and API.
Preserved the original filesystem path during indexing instead of storing temporary upload paths.
Added hash-based checks to avoid unnecessary re-indexing during the initial folder scan.
Added support for processing ZIP archives by extracting and indexing their contents.
Implemented event debouncing in the Watchdog client to reduce duplicate indexing triggered by rapid filesystem events.
Added background indexing using FastAPI background tasks.
Testing
Verified the following workflow:
Existing files are indexed during startup.
Newly created files are indexed automatically.
File modifications trigger re-indexing.
File deletions remove indexed records.
File renames update the stored file path.
ZIP archives are extracted and processed successfully.
Indexed files are visible through the /files API.
Notes
Embedding generation currently loads models synchronously and can be slow when indexing many files. Optimising the embedding pipeline and model lifecycle is planned separately.
Support for filtering unsupported file types will be added in a future PR.