<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Unstructured Data on Wiliam Rosa | Lakehouse, Dados &amp; IA</title>
    <link>https://wiliamrosa.github.io/tags/unstructured-data/</link>
    <description>Recent content in Unstructured Data on Wiliam Rosa | Lakehouse, Dados &amp; IA</description>
    <image>
      <title>Wiliam Rosa | Lakehouse, Dados &amp; IA</title>
      <url>https://wiliamrosa.github.io/images/wiliam-rosa-blog-og.png</url>
      <link>https://wiliamrosa.github.io/images/wiliam-rosa-blog-og.png</link>
    </image>
    <generator>Hugo</generator>
    <language>pt-br</language>
    <lastBuildDate>Fri, 17 Apr 2026 09:00:00 -0300</lastBuildDate>
    <atom:link href="https://wiliamrosa.github.io/tags/unstructured-data/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>De PDF solto a coluna de tabela: o pipeline que domestica documento não estruturado no lakehouse</title>
      <link>https://wiliamrosa.github.io/articles/databricks-document-intelligence-pipeline-documentos-nao-estruturados/</link>
      <pubDate>Fri, 17 Apr 2026 09:00:00 -0300</pubDate>
      <guid>https://wiliamrosa.github.io/articles/databricks-document-intelligence-pipeline-documentos-nao-estruturados/</guid>
      <description>ai_parse_document, ai_extract e ai_classify já são GA no Azure Databricks, e o pipeline de processamento inteligente de documento (IDP) inteiro roda dentro do Lakeflow, sem infraestrutura separada de OCR ou fila de mensagem. A peça que ainda é Beta, ai_prep_search, é justamente a que decide se o documento processado vira retrieval bom ou lixo semântico.</description>
    </item>
  </channel>
</rss>
