spark-version-upgrade skillA
spark-version-upgrade is agent-read markdown (skill) from openhands/extensions: Upgrade Apache Spark applications between major versions (2.x→3.x, 3.x→4.x). Covers build files, deprecated APIs, configuration changes, SQL/DataFrame updates, and test validation..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
Upgrade Apache Spark applications between major versions with a structured, phase-by-phase workflow. ## When to Use - Migrating from Spark 2.x → 3.x or Spark 3.x → 4.x - Updating PySpark, Spark SQL, or Structured Streaming applications - Resolving deprecation warnings before a Spark version bump ## Workflow Overview 1. **Inventory & Impact Analysis** — Scan the codebase and assess scope 2. **Build File Updates** — Bump Spark/Scala/Java dependencies 3. **API Migration** — Replace deprecated and removed APIs 4. **Configuration Migration** — Update Spark config properties 5. **SQL & DataFrame Migration** — Fix query-level breaking changes 6. **Test Validation** — Compile, run tests, verify results --- ## Phase 1: Inventory & Impact Analysis Before changing any code, assess what needs to change. Read the official Apache Spark migration guide for the target version — it documents every API removal, config rename, and behavioral change per release: https://spark.apache.org/docs/latest/migration-guide.html ### Checklist - [ ] Read the migration guide section for the target Spark version …
Read the whole file at its exact version.
How to install
mdr add openhands/extensions/spark-version-upgrade@git:20260701.599cc4dmdr add openhands/extensions/spark-version-upgrade@sha256:4351d37aec3b7b19Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_xhnujy6lvz3iwhcg)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260701.599cc4d latest | 2026-07-01 | 599cc4d | 7,777 B | A | view · diff |
| git:20260406.ef5a6c2 | 2026-04-06 | ef5a6c2 | 7,592 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7777 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
openhands/extensions · 150 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xhnujy6lvz3iwhcg GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/spark-version-upgrade GET https://markdownregistry.com/api/v1/blob/4351d37aec3b7b19cc52bba87aaa8c48c67c0ee4a50e73afcb175aeca4fe4762
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.