fabric-lakehouse

Solid

Use this skill to get context about Fabric Lakehouse and its features for software systems and AI-powered functions. It offers descriptions of Lakehouse data components, organization with schemas and shortcuts, access control, and code examples. This skill supports users in designing, building, and optimizing Lakehouse solutions using best practices.

AI & Automation 34,887 stars 4287 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# When to Use This Skill Use this skill when you need to: - Generate a document or explanation that includes definition and context about Fabric Lakehouse and its capabilities. - Design, build, and optimize Lakehouse solutions using best practices. - Understand the core concepts and components of a Lakehouse in Microsoft Fabric. - Learn how to manage tabular and non-tabular data within a Lakehouse. # Fabric Lakehouse ## Core Concepts ### What is a Lakehouse? Lakehouse in Microsoft Fabric is an item that gives users a place to store their tabular data (like tables) and non-tabular data (like files). It combines the flexibility of a data lake with the management capabilities of a data warehouse. It provides: - **Unified storage** in OneLake for structured and unstructured data - **Delta Lake format** for ACID transactions, versioning, and time travel - **SQL analytics endpoint** for T-SQL queries - **Semantic model** for Power BI integration - Support for other table formats like CSV, Parquet - Support for any file formats - Tools for table optimization and data management ### Key Components - **Delta Tables**: Managed tables with ACID compliance and schema enforcement - **Files**: Unstructured/semi-structured data in the Files section - **SQL Endpoint**: Auto-generated read-only SQL interface for querying - **Shortcuts**: Virtual links to external/internal data without copying - **Fabric Materialized Views**: Pre-computed tables for fast query performance ### Tabular ...

Details

Author
github
Repository
github/awesome-copilot
Created
1 years ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

fabric-lakehouse-perf-remediate

Diagnose and resolve Microsoft Fabric Lakehouse performance issues including slow Spark queries, small file problems, Delta table fragmentation, V-Order configuration, table maintenance (OPTIMIZE, VACUUM, Z-Order), SQL analytics endpoint tuning, Direct Lake performance, resource profile selection, autotune configuration, capacity throttling, and streaming ingestion optimization. Use when asked to troubleshoot Fabric Lakehouse slowness, optimize Delta tables, fix small file problems, configure Spark settings, run table maintenance, or improve query performance in notebooks or pipelines.

13 Updated 4 days ago
PatrickGallucci
Data & Documents Listed

fabric-lakehouse-access-control

Troubleshoot Microsoft Fabric Lakehouse access control issues including OneLake security roles, SQL analytics endpoint permissions, workspace roles, data access roles, row-level security (RLS), column-level security (CLS), object-level security (OLS), dynamic data masking, shortcut permissions, Direct Lake security integration, DefaultReader role, ReadAll permission, and OneLake data access role conflicts. Use when users report permission denied, unauthorized access, missing data, empty query results, or cannot see tables in Fabric Lakehouse.

13 Updated 4 days ago
PatrickGallucci
API & Backend Listed

fabric-spark

Use for PySpark / Spark in Microsoft Fabric notebooks. Covers the no-external-HTTP constraint (land data in Files/ first), abfss:// URI format for OneLake (GUIDs not names), `notebookutils.runtime.context` for identity lookups vs `spark.conf.*` for session tuning, mssparkutils, lakehouse `enableSchemas` immutability and cross-lakehouse 3-part names, table maintenance (OPTIMIZE/VACUUM/V-Order) impact on SQL Endpoint, Delta Lake default, REST notebook upload quirks (bare-string source `400 exceptionCulprit:1`, `metadata.dependencies.lakehouse` for default-lakehouse binding, 411 on empty-body getDefinition, `/result` LRO suffix, `?updateMetadata=true` requires `.platform`), notebook-execution gotchas (`defaultLakehouse` needs id+name, never retry POST), and in-notebook auto-restart via `%%configure retriableOptions { enabled, maxAttempt }` (April 2026, for pipeline-driven runs).

1 Updated 1 weeks ago
wardawgmalvicious