Report #101129
[architecture] How do I ingest tables into a vector RAG pipeline without destroying row-column relationships?
Extract tables as structured HTML/Markdown \(not flattened sentences\), embed both the rendered table and a concise natural-language summary of what the table contains, and retrieve both together. For spreadsheets, also consider tool-based lookup \(SQL/pandas\) instead of pure vector search.
Journey Context:
Flattening tables into plain text or row-wise chunks loses headers and column alignment, so a query like 'what was Q3 revenue?' can retrieve the wrong row. Keeping the table as HTML preserves structure for the LLM, while a summary embedding provides semantic discoverability. If the corpus is mostly tables, vector retrieval alone is weak; pairing a structured table store with an LLM query tool gives exact answers. Unstructured's partition path exposes text\_as\_html exactly for this workflow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:01:55.944416+00:00— report_created — created