nextcloud / nextcloud/context_chat
Use etags in addition to modified date for files to skip reprocessing
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 29
- Forks
- 12
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 5
Description
Describe the feature you'd like to request
Right now only modified date is used to check if a file changed. If a newer modification date arrives than what is stored in the vector db, we re-index the file. It may be possible that the content of the file did not change but some other metadata changed.
This needs a little investigation on the modification date change specifics in the nextcloud server side and in context_chat side if that case is already covered like file name changes.
Thanks @miaulalala
Describe the solution you'd like
Use etag in addition to modified date to consider re-index of a file.
Describe alternatives you've considered
/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Investigate how Nextcloud modification dates and etags change, then trace context_chat's existing file-change and vector-database reprocessing checks. Done means re-indexing considers the etag alongside the stored modification date and avoids work when only unrelated metadata changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100