Repository navigation
docs(ingest): blank scans and text-free photos fail with E2002 (PRO-2456) - #313
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
✅ Mintlify HygieneNo issues found. |
|
✅ OpenHack SummarySecurity review of docs(ingest): blank scans and text-free photos fail with E2002 (PRO-2456). 2 changed files; 0 findings at or above the low reporting threshold. Confidence Score: 5/5No reportable security findings were detected in this scan. Security merge-readiness rubric: 1 = critical, 2 = high, 3 = medium, 4 = low, 5 = no reportable findings. This score reflects scan findings, not a guarantee of correctness or complete coverage. Files Needing Attention: None Important Files Changed
Last reviewed commit: 4fb2032 · View review on OpenHack
|
…456)
The supported-formats section said a scan or photo with no readable text
'will index as an empty document rather than fail'. It actually indexed an
empty OCR code fence; with that fixed, such a file now ends errored with E2002
('No text content could be extracted'), which is terminal. Document that, and
add E2002 to the ingestion error-code table.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Aditya Shrivastava <aditya@hydradb.com>
7e289b4 to
4fb2032
Compare
Part of PRO-2456. Merge only when the companion code ships: hydra-db/hydradb-application#2057 (Go Stage A, which serves
POST /context/ingestdocuments) and hydra-db/cortex-ingestion#911.What changes for customers
The "Supported file formats" section of
ingest-contextsaid:That was never quite true. LiteParse emitted an empty
```textcode fence for such pages, and that fence was what got indexed. With the fence fixed, a binary file with no extractable text now endserroredwithE2002. Customers see the message "No text content could be extracted from your file. Please ensure it isn't empty or image-only." It is terminal: the same file gives the same result. A multi-page scan with readable text on any page still indexes normally.Changes
api-reference/v2/endpoint/ingest-context.mdx: replace that sentence with the actual behaviour, linking to the error code.api-reference/v2/error-responses.mdx: add anE2002row to the ingestion error-codes table (meaning, user message, terminal).Not changed: connector and app-source docs. The other PRO-2456 work, Gemini transcription and description of connector image attachments, changes no API surface or behaviour that customers call directly.
🤖 Generated with Claude Code