Skip to main content
Unstructured recommends that you save the extracted JSON data only to a blob storage, file storage, or No-SQL database destination location. For the extracted data only output format, Unstructured’s destination connectors cannot insert custom JSON objects into a SQL-style database or vector store. Instead, save the extracted JSON to blob storage, file storage, or a NoSQL database. Then use your own code to insert the data into your target destination. For the elements with extracted data output format, Unstructured does not recommend that you save DocumentData elements as rows, records, or entries within a traditional SQL-style destination database or vector store either, for the following reasons:
  • Saving a mixture of DocumentData elements and default Unstructured elements such as Title, NarrativeText, and Table elements and so on in the same table, collection, or index might cause unexpected performance issues or might return less useful search and query results.
  • The DocumentData elements’ extracted_data contents can get quite large and complex, exceeding the column or field limits of some SQL-style databases or vector stores.
For how structured values are wrapped in workflow JSON (elements with extracted data vs extracted data only), see Custom defined output.