gcp-spark
Develops, optimizes and runs PySpark/Spark code on Managed Spark (Dataproc clusters and Serverless) on Google Cloud. Use when: - Authoring or running Spark/PySpark notebooks (any kernel), incl. data analysis, reports and visualizations. - Writing Spark ETL pipelines or preparing workloads for production. - Training or running inference with ML models on Spark. - Optimizing PySpark or Spark SQL for performance, memory, or OOM risks. - Managing Spark clusters, jobs, batches, and interactive sessions. Don't use when: - Writing generic Python that doesn't use Spark. - Performing simple SQL queries that can be done directly in BigQuery. - Troubleshooting failed Spark workloads (use @skill:gcp-spark-troubleshooting).
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- gcp-spark
- license
- Apache-2.0
- metadata
- { "version": "v24", "publisher": "google" }
- description
- Develops, optimizes and runs PySpark/Spark code on Managed Spark (Dataproc clusters and Serverless) on Google Cloud. Use when: - Authoring or running Spark/PySpark notebooks (any kernel), incl. data analysis, reports and visualizations. - Writing Spark ETL pipelines or preparing workloads for production. - Training or running inference with ML models on Spark. - Optimizing PySpark or Spark SQL for performance, memory, or OOM risks. - Managing Spark clusters, jobs, batches, and interactive sessions. Don't use when: - Writing generic Python that doesn't use Spark. - Performing simple SQL queries that can be done directly in BigQuery. - Troubleshooting failed Spark workloads (use @skill:gcp-spark-troubleshooting).
02 资源文件 6
- 参考文档references/gcloud_dataproc.md12.6 KB
- 参考文档references/ml_tasks.md3.0 KB
- 参考文档references/read_write_data.md20.3 KB
- 参考文档references/schema_direct_inspection.md1.3 KB
- 参考文档references/spark_optimizations.md7.2 KB
- 参考文档references/spark_refactoring_guide.md2.5 KB
03 SKILL.md 正文
Managed Spark on Google Cloud
[!IMPORTANT]
You MUST follow the Task Execution Workflow when writing spark code.
Notebook Generation Environment Rules
[!CAUTION]
When the task is to generate a Spark notebook (as opposed to executing one), you MUST NOT modify your own local execution environment (i.e. do not run these commands with your shell or other tools). Specifically:
- NEVER create a virtual environment (
python -m venv,virtualenv,conda create,uv venv,poetry init/install, etc.).- NEVER install packages (
pip install,%pip install,uv pip install,conda install,poetry add).- NEVER run environment discovery loops such as activating a venv,
pip list, or probing foripykernel/google-cloud-spark-connectas a precondition for writing the notebook.Assume the user will select the appropriate kernel and dependencies after the notebook is generated.
Task Execution Workflow
-
Understand user request:
- When asked to generate a new spark notebook you MUST clarify with
the user which kernel type will be used: "Local Python" (Spark Connect)
or "Remote Spark". If the user selects "Local Python", you MUST
additionally clarify which dataprocSessionConfig should be used (scan
for existing serverless session templates), and MUST initialize the
session with
ManagedSparkSessionby adding the following cells to the notebook:from google.cloud.dataproc_v1 import Session # requires google-cloud-spark-connect pypi package for execution from google.cloud.managed_spark_connect import ManagedSparkSession session_config = Session() session_config.session_template = ( "projects/<PROJECT_ID>/locations/<REGION>/sessionTemplates/<TEMPLATE_ID>" ) spark = ( ManagedSparkSession.builder.projectId("<PROJECT_ID>") .location("<REGION>") .dataprocSessionConfig(session_config) .getOrCreate() )
- When asked to generate a new spark notebook you MUST clarify with
the user which kernel type will be used: "Local Python" (Spark Connect)
or "Remote Spark". If the user selects "Local Python", you MUST
additionally clarify which dataprocSessionConfig should be used (scan
for existing serverless session templates), and MUST initialize the
session with
-
Understand schemas: ALWAYS use
@skill:discovering-gcp-data-assetsskill orreferences/schema_direct_inspection.mdto understand input and output schemas. Include the schema in your thought process BEFORE generating any code. Do NOT guess column names. Cap GCP data asset discovery attempts at 3 retries max. Unless explicitly specified, assume that the assets are located in the same project. Avoid scanning for assets across other projects as it can take a long time. If an expected dataset or table does not exist, use@skill:discovering-gcp-data-assetsto discover all similar tables in the namespace or project.MINOR TYPO RULE: If there is a minor typo (e.g.
employeesvsemployee), you can fix the error and proceed.STRICT HALT RULE: If the discovered table names differ from the requested table by more than a minor typo (e.g. completely different words, prefixes, or suffixes), you must IMMEDIATELY report the missing table and a neutral list of all available alternatives in the same namespace to the user without making any recommendations. You MUST ask the user which alternative to use and then STOP EXECUTING your turn. Do NOT write any Spark code or notebooks. Do NOT proceed with code generation, do NOT add fallback logic to code, and do NOT automatically substitute any alternative table (even if its schema seems to match) without explicit user permission.
-
Verify source accessibility: verify access/existence using
gcloud storage ls gs://<path-to-dataset>. If accessing or reading a GCS path fails with a storage error e.g., permission errors like403 Forbidden/Forbidden/PermissionDenied, or location errors like404 Not Found/NotFound/FileNotFoundExceptionyou should report the error immediately. Either (1) ask the user what to do next, or (2) if asked to execute a notebook, save the notebook with the error output and recommend next steps to resolve the issue. Do NOT scan all buckets for alternative fallback datasets when encountering GCS errors. -
Generate spark code:
-
Output Format: ALWAYS generate code in Python Notebooks (.ipynb) format. Generate scripts (.py) only if explicitly requested.
-
Spark Session Initialization:
[!IMPORTANT] Initializing a Spark session on Google Cloud can take 2-3 minutes. You MUST inform the user about the potential delay.
[!CAUTION] NEVER create a local Spark session. The following are BANNED: -
SparkSession.builder.master("local")-pyspark.sql.SparkSession.builder.getOrCreate()in notebooks or local Spark Connect scripts when used withoutManagedSparkSession- Anytry/exceptfallbacks that revert to a localSparkSession.- Interactive Notebooks (
.ipynb) & Spark Connect scripts: You MUST ALWAYS useManagedSparkSessionfromgoogle-cloud-spark-connectto connect to Managed Spark Serverless. No exceptions. - Dataproc Batch & Cluster jobs (
.pysubmitted viagcloud dataproc batches submit pysparkorgcloud dataproc jobs submit pyspark): Use standardSparkSession.builder.appName("<APP_NAME>").getOrCreate()(never.master("local")).
Refer to
references/gcloud_dataproc.mdfor detailed configuration. Minimal initialization for notebooks / Spark Connect:from google.cloud.managed_spark_connect import ManagedSparkSession spark = ManagedSparkSession.builder.projectId(<PROJECT_ID>) .location(<REGION>) .getOrCreate() - Interactive Notebooks (
-
Production Logging: In standalone production PySpark batch jobs and scripts (
.py), you MUST use the standard Pythonloggingmodule instead ofprint()statements for job lifecycle, progress, and record counts. Do NOT use theloggingmodule in notebooks (.ipynb); useprint(),.show(), and standard cell outputs instead. Configureloggingfor.pyscripts with timestamps:import logging logging.basicConfig( level=logging.INFO, format="%(asctime)s [%(levelname)s] %(message)s", ) -
Security & Dynamic Variables: You MUST NOT hardcode plaintext credentials, passwords, or tokens (use Secret Manager). You MUST NOT hardcode environment-specific variables; parameterize project IDs, dataset IDs, table names, and bucket paths via
os.environ.get(...)or arguments. -
Read and Write data: ALWAYS Refer to
references/read_write_data.mdwhen reading or writing data. -
Machine Learning Tasks: Refer to
@skill:ml-best-practicesskill andreferences/ml_tasks.mdwhen generating Machine Learning code. -
Spark Optimizations & Broadcast Joins: ALWAYS refer to
references/spark_optimizations.md. When joining a large DataFrame with a small lookup or dimension table, you MUST usebroadcast()(from pyspark.sql.functions import broadcast) on the small table. Treat about 10 MB (Spark's defaultspark.sql.autoBroadcastJoinThreshold) as a guide to what counts as small, not a hard limit.
-
-
Verify schema before write: ALWAYS verify that the dataframe and destination schema match, use
df.printSchema()for dataframe schema and refer to@skill:discovering-gcp-data-assetsskill orreferences/schema_direct_inspection.mdto verify destination schema. -
Compile code before executing: For notebooks convert them to python script using
jupyter nbconvert --to script your-notebook.ipynbfirst. Then compile the resulting python script usingpython3 -m py_compile your-script.py. The same can be done for pyspark source code. -
Execute script or notebook: When requested to run a job, script, session, or execute notebook cells against Managed Spark, refer to
references/gcloud_dataproc.mdon how to execute code on Dataproc Serverless using Spark Connect or Dataproc jobs. -
Follow up with the user: If a brand new notebook was generated, instruct the user to select the appropriate kernel in the dropdown for cell execution.
Common Mistakes Checklist
[!CAUTION]
Ensure you verify this checklist to avoid mistakes
Before submitting a job, verify:
- [ ] All imports present (
col,when,lit,broadcast, etc. frompyspark.sql.functions) - [ ]
vector_to_arrayfrom correct module usefrom pyspark.ml.functions import vector_to_array(NOTpyspark.sql.functions) - [ ] DataFrame schema matches target Iceberg table verify with
df.printSchema()before writing - [ ] CSV files read with
headerandinferSchemawithout these, the header row becomes data and all columns are strings - [ ] Driver memory safety (
toPandas()/collect()) NEVER call.toPandas()or.collect()on raw or un-aggregated DataFrames. ALWAYS perform transformations, aggregations (groupBy().agg()), or data reduction (limit(),sample()) in Spark before converting small summaries to Pandas for plotting or display. - [ ] No inline pip install in Spark batch/script jobs: NEVER run pip
install or subprocess package installations inside PySpark batch scripts
(the
%pip installsetup cell in generated notebooks is exempt). Pass dependencies using --properties=spark.jars.packages=..., --archives=gs://.../env.tar.gz#environment, --py-files, or a custom --container-image. - [ ] Optimization & Pre-Submission Refactoring Verify the job against
references/spark_optimizations.mdand follow the confirmation protocol inreferences/spark_refactoring_guide.md. - [ ] No full file reads of executed notebooks: You MUST NOT use
read_fileor generic full file reading tools on executed.ipynbnotebooks; they often contain massive base64-encoded image outputs that cause excessive token consumption. You MUST inspect execution outputs with cell-scoped reading tools (such asnotebook__read_cell,jupyter__read_cell, or specific line slices).
IAM Requirements
The Managed Spark (Dataproc) service account needs:
roles/dataproc.worker: Job executionroles/biglake.admin: BigLake Iceberg table managementroles/bigquery.jobUser: BigQuery query materialization and load jobsroles/bigquery.dataEditor: BigQuery table reads and writes (direct and indirect)roles/bigquery.readSessionUser: BigQuery Storage Read API session creationroles/storage.objectUser: Read/write GCS (data, Iceberg warehouse, and--deps-bucket/temporaryGcsBucket)roles/spanner.databaseUser: Spanner reads and writes
Spark resource management
Refer to references/gcloud_dataproc.md for detailed guidelines on managing
Spark clusters, jobs, batches, interactive sessions, and Spark Connect sessions.
Code Optimization & Pre-Submission Verification
Before submitting any Spark job or Dataproc batch, enforce the pre-submission
verification protocol in references/spark_refactoring_guide.md: inspect the
code for the anti-patterns catalogued in references/spark_optimizations.md and
obtain explicit user confirmation before applying refactoring.
Troubleshooting & Root Cause Analysis
For troubleshooting failed Spark jobs or Dataproc batches, inspecting/tailing
GCS driver output logs, analyzing Spark event logs, or performing Root Cause
Analysis (RCA), use the @skill:gcp-spark-troubleshooting skill.
04 同仓库更多 Skills
rag-architect-agent
Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon/Supabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).
rag-architecture-patterns
Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).
skill-repair
Use this to fix and re-install agent skills that have failed installation. This skill provides the necessary context and permissions to surgically update the `manifest.json` after a fix has been applied.
security-scan
Scan your Claude Code configuration (.claude/ directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.
security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
security-bounty-hunter
Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.