What problem does it solve?
Working with Microsoft Fabric Spark requires juggling notebook authoring, Livy session management, job failure triage, and Materialized Lake View (MLV) operations across many REST endpoints, and mistakes like wrong payload shapes or missed terminal writes produce silent failures.
Core Features & Use Cases
- Notebook authoring and execution: Write PySpark, Scala, SparkR, %%sql, and %%configure cells, save them via updateDefinition, and run named notebooks through the Jobs API.
- Interactive Livy sessions: Create and reuse Lakehouse Livy sessions for ad-hoc PySpark analysis, cross-lakehouse queries, and Delta time-travel.
- Spark failure diagnostics: Triage failed, slow, or OOM notebook and pipeline runs using the Spark Advisor API, monitoring APIs, and log retrieval.
- Materialized Lake View lifecycle: Author MLV definitions, review queries for incremental-refresh readiness, schedule refreshes, trigger on-demand runs, and diagnose refresh failures.
- Use Case: A user asks why their nightly notebook failed; the skill resolves the workspace, queries the Spark Advisor, identifies an OutOfMemoryError with data skew, and reports the root cause with a Notebook Snapshot link.
Quick Start
Ask the assistant to diagnose why your Fabric notebook run failed, or to schedule a nightly refresh for a Materialized Lake View in your lakehouse.