界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
设计与创意 · SKILL.md

data-lake

data-lake

【设计与创意】Use when designing, building, or managing data lakes — zone architecture (raw/cleansed/curated/consumption), data catalog and governance, file formats (Parquet/ORC/Avro/Delta Lake/Apache Iceberg), storage layout and partitioning, schema evolution, Spark/Trino/Presto query engines, data quality frameworks, lakehouse patterns, and cloud/on-prem storage…

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: data-lake description: Use when designing, building, or managing data lakes — zone architecture (raw/cleansed/curated/consumption), data catalog and governance, file formats (Parquet/ORC/Avro/Delta Lake/Apache Iceberg), storage layout and partitioning, schema evolution, Spark/Trino/Presto query engines, data quality frameworks, lakehouse patterns, and cloud/on-prem storage (S3/ADLS/HDFS/MinIO). Part of the data-* skill family.

Data Lake Architecture & Implementation

For related skills see: python-data-engineer (SQLAlchemy, Alembic, DB admin), python-enterprise-connectors (DB2, Oracle, mainframe), docker-compose-patterns (containerized Spark/Trino), large-file-analysis (CSV/log processing).


Reference Files

Detailed code examples, patterns, and configuration are in the reference files below. Read the relevant file when working on that area.

FileCovers
formats-catalog-engines.mdfile formats (Parquet/ORC/Avro), table formats (Delta Lake/Apache Iceberg/Apache Hudi), data catalog/governance, and query engines
fundamentals-zones-storage.mdlake vs warehouse vs lakehouse comparison, zone architecture (raw/cleansed/curated/consumption), and storage layer configuration
quality-ingestion-security.mdschema evolution patterns, data quality frameworks, ingestion patterns, and security/access control


Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
Dumping raw data without zone separationData lake becomes a data swamp; no one knows what is clean, what is raw, what is trustedImplement zone architecture: raw (landing), cleansed (validated), curated (business-ready), consumption (optimized)
No data catalog or metadata managementUsers cannot find data; duplicate datasets proliferate; lineage is unknown; compliance audits failDeploy a data catalog (Apache Atlas, AWS Glue Catalog); tag every dataset with owner, schema, lineage, and classification
Storing everything as CSVNo schema enforcement, no compression, no predicate pushdown; queries scan entire filesUse columnar formats (Parquet, ORC) for analytics; Avro for streaming; Delta Lake/Iceberg for ACID and time travel
No partition strategy for large datasetsFull table scans on billions of rows; queries take hours instead of secondsPartition by date and high-cardinality filter columns; align partition granularity with query patterns
Treating the data lake as append-only with no lifecycle managementStorage costs grow unbounded; stale data pollutes queries; compliance (GDPR right-to-delete) becomes impossibleImplement retention policies per zone; archive cold data to cheaper storage tier; enable deletion for compliance

Related Skills

DomainSkill
Database admin (SQLAlchemy, Alembic, query optimization)python-data-engineer
Enterprise DB connectors (DB2, Oracle, mainframe)python-enterprise-connectors
Containerized infrastructure (Spark/Trino in Docker)docker-compose-patterns
Large file processing strategieslarge-file-analysis
Python parallelism (asyncio, multiprocessing, Dask)python-parallelism
Web research for technology evaluationweb-research
我的收藏