Language:JapaneseEnglish

oracle-ai-data-platform-workbench-databricks-migrator Claude Code Plugin

Author
Oracle
Category
Development
Topics
Migration & Modernization · Data Engineering & Analytics · Databases & Storage
First cataloged
2026-07-09 (UTC)
Explanation last updated
2026-07-16 (UTC)
Source (GitHub) last updated
2026-06-25 (UTC) (63 days ago)

The explanation below is AI-generated. Please verify it against the sources.

This plugin lets a user drive, through natural-language requests in Claude Code, an automated toolkit that migrates Databricks notebooks, jobs, schedules, and catalog definitions onto Oracle AI Data Platform (AIDP). According to the README, it bundles a Python migration engine that works in two passes: a first pass that rewrites code dependencies, and a second pass that executes each notebook cell on a live AIDP cluster, checks the result, and attempts automatic fixes when a cell fails. It also converts Unity Catalog or Hive Metastore definitions using a set of DDL rewrite rules and maps S3 storage paths to OCI storage locations. The plugin ships a set of skills covering setup checks, migration planning, job execution, catalog conversion, and post-migration verification, along with guided slash commands and reviewer agents. Running an actual migration additionally requires OCI credentials, an active AIDP cluster, and an Anthropic API key, as stated in the README's prerequisites section.

About the service

Oracle AI Data Platform Workbench, as described on its own homepage, is a cloud service for cataloging, ingesting, and analyzing organizational data, and it provides the underlying platform for building data pipelines, AI agents, and machine learning workflows. This plugin connects that service to an existing Databricks environment, transferring notebooks, job definitions, schedules, and catalog metadata from Databricks into AIDP's data lake and compute cluster.

What you can do with oracle-ai-data-platform-workbench-databricks-migrator

  • Ask Claude to build a migration manifest and dependency map from a Databricks workspace path
  • Check whether source tables and paths are ready on the AIDP cluster before starting a migration
  • Run a full job migration combining dependency rewriting and live cell-by-cell execution with verification
  • Target a specific failing cell for re-execution or resume an interrupted migration run
  • Migrate Unity Catalog or Hive Metastore DDL with automated rewrite rules and S3-to-OCI bucket mapping
  • Configure acceptance criteria for batch or streaming jobs based on convergence checks
  • Use guided slash commands for full migration, catalog migration, data checks, and status reporting
  • Have specialist agents analyze a source notebook or review a migrated notebook for correctness

Sources

Back to list