api: questions on long PDFs are answered (retrieval in the digest meta); README and skill
The digest now handles long documents itself (task 02), so the API's refusal limit is only a safety cap: DefaultPDFMaxQuestionChunks 200 -> 5000 (the 422 message text is unchanged). In v1fetch the digest-meta object gains "retrieval" and "embedded" next to chunks_used/chunks_total, only when the digest ran without a fallback. The PDF section explains a long-doc question is answered first from BM25 while its chunks embed in the background and hybrid on later questions; skill/SKILL.md gains one sentence. Given tests byte-identical. Co-Authored-By: ornith-1.5-35b-a3b <ornith-1.5-35b-a3b@llama.cpp.invalid>
This commit is contained in:
+5
-3
@@ -20,9 +20,11 @@ import (
|
||||
const (
|
||||
// DefaultPDFTTL is how long a cached PDF is served before it is revalidated.
|
||||
DefaultPDFTTL = 24 * time.Hour
|
||||
// DefaultPDFMaxQuestionChunks is the longest document (in digest chunks) a question is
|
||||
// answered over; a longer one is refused in favour of grep or pages.
|
||||
DefaultPDFMaxQuestionChunks = 200
|
||||
// DefaultPDFMaxQuestionChunks is the safety cap on how long a document a question is
|
||||
// answered over; beyond it the question is refused in favour of grep or pages. Longer
|
||||
// documents are handled by retrieval (BM25 first, embedding their chunks in the
|
||||
// background), so this only bounds the un-answerable.
|
||||
DefaultPDFMaxQuestionChunks = 5000
|
||||
)
|
||||
|
||||
// runner returns the configured extraction child, or a zero Runner that runs
|
||||
|
||||
Reference in New Issue
Block a user