<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tutorial on Apache Airflow</title>
    <link>/blog/tags/tutorial/</link>
    <description>Recent content in Tutorial on Apache Airflow</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 16 Apr 2026 01:48:55 +0100</lastBuildDate>
    <atom:link href="/blog/tags/tutorial/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agentic Workloads on Airflow: Observable, Retryable, and Auditable by Design</title>
      <link>/blog/agentic-workloads-airflow-3/</link>
      <pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/blog/agentic-workloads-airflow-3/</guid>
      <description>&lt;p&gt;A question like &amp;ldquo;How does AI tool usage vary across Airflow versions?&amp;rdquo; has a natural SQL shape: one cross-tabulation, one result. A question like &amp;ldquo;What does a typical Airflow deployment look like for practitioners who are actively using AI in their workflow?&amp;rdquo; does not. It requires querying executor type, deployment method, cloud provider, and Airflow version independently, each filtered to the same respondent group, then synthesizing the results into a coherent picture. No single query returns the answer. The answer emerges from the relationship between all of them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ask Your Survey Anything: Building AI Analysis Pipelines with Airflow 3</title>
      <link>/blog/ai-survey-analysis-pipelines/</link>
      <pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/blog/ai-survey-analysis-pipelines/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://airflow.apache.org/survey/&#34;&gt;2025 Airflow Community Survey&lt;/a&gt; collected responses&#xA;from nearly 6,000 practitioners across 168 questions. You can open a spreadsheet and filter,&#xA;or write SQL by hand. But what if you could just ask a question and have Airflow figure out&#xA;the query, run it, and bring the result back for your approval?&lt;/p&gt;&#xA;&lt;p&gt;This post builds two pipelines that do exactly that, using the&#xA;&lt;a href=&#34;https://pypi.org/project/apache-airflow-providers-common-ai/&#34;&gt;&lt;code&gt;apache-airflow-providers-common-ai&lt;/code&gt;&lt;/a&gt;&#xA;provider for Airflow 3.&lt;/p&gt;&#xA;&lt;p&gt;The first pipeline is &lt;strong&gt;interactive&lt;/strong&gt;: a human reviews the question before it reaches the LLM&#xA;and approves the result before the DAG finishes. The second is &lt;strong&gt;scheduled&lt;/strong&gt;: it downloads&#xA;fresh survey data, validates the schema, runs the query unattended, and emails the result.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
