Add Auto Loader reference to SDP skill#539
Open
jralfonsog wants to merge 1 commit into
Open
Conversation
Consolidates Auto Loader fundamentals into a single reference file in the SDP skill. Default examples assume SDP context (managed checkpoints and schema location); a quick-start for raw Structured Streaming is included for non-SDP usage. Adds a pointer from the structured streaming skill so non-SDP users can find it. Co-authored-by: Isaac
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Consolidates Auto Loader fundamentals into a single reference file in the SDP skill, with a pointer from the Structured Streaming skill for non-SDP users. Follows @QuentinAmbard's call in #ai-dev-kit-team (standalone Auto Loader skill was overkill; fundamentals belong as an SDP reference).
databricks-skills/databricks-spark-declarative-pipelines/references/auto-loader.md(957 lines) — consolidated from an earlier 8-file draft. Default examples assume SDP context (managed checkpoints, managed schema location). Includes a "raw Structured Streaming" quick-start for non-SDP usage with the explicit checkpoint-and-schema-path caveat.databricks-skills/databricks-spark-declarative-pipelines/references/python/2-ingestion.md— intro touch-up + pointer to../auto-loader.mdfor the deep dive.databricks-skills/databricks-spark-structured-streaming/streaming-best-practices.md(section 2) — replaces the inline Auto Loader snippet with a pointer to the canonical SDP reference, preserving the non-SDP checkpoint caveat at the call site.Why
Auto Loader is fundamentally an ingestion pattern, and ingestion is owned by the SDP skill. The previous structure (standalone draft) duplicated coverage and gave no obvious home for the SDP-vs-raw-streaming distinction. Single canonical reference + skill-level pointer keeps the content discoverable from both entry points without duplication.
Routing
Targeting
mainper the "send to main, we'll cherry-pick to experimental" pattern @calreynolds and @QuentinAmbard established on #498. Happy to rebase if a different routing is preferred.Test plan
auto-loader.mdrenders cleanly (957 lines, sections: Quick start, SDP defaults, Raw Structured Streaming, Schema evolution, File listing modes, Backfill, Operational gotchas, Troubleshooting).2-ingestion.mdandstreaming-best-practices.mdresolve to../auto-loader.mdcorrectly.checkpointLocation/cloudFiles.schemaLocation(managed by SDP); the raw-streaming quick-start does.This pull request was AI-assisted by Isaac.