azure-hdinsight-migration-hbase-to-fabric-cosmosdb

Orchestrate HDInsight HBase migration to Cosmos DB with Fabric mirroring.

Updated Apr 27, 2026

Search Tags:#fabric #cosmosdb #schema-design #data-migration #hdinsight #partition-key #hbase

Ready to run

npx skills add https://github.com/tomz/agent-skills --skill azure-hdinsight-migration-hbase-to-fabric-cosmosdb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azure-hdinsight-migration-hbase-to-fabric-cosmosdb
Source: https://github.com/tomz/agent-skills/tree/main/azure-hdinsight-migration-hbase-to-fabric-cosmosdb
Command: npx skills add https://github.com/tomz/agent-skills --skill azure-hdinsight-migration-hbase-to-fabric-cosmosdb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migration of large HDInsight HBase workloads to Cosmos DB and Fabric mirroring is complex, error-prone, and time-consuming; this Skill provides a comprehensive guide to plan, architect, and execute end-to-end migrations with schema redesign, key translation, throughput sizing, bulk export, client SDK rewrites, and security alignment to minimize risk and downtime.

Core Features & Use Cases

End-to-end migration playbook from HDInsight HBase to Cosmos DB (NoSQL or Cassandra) with Fabric mirroring for analytics.
Schema redesign guidance (column-family to JSON/wide-column, row-key to partition-key mapping) and RU/s sizing strategies.
Guidance on bulk data movement, client SDK rewrites, and security mapping for a smooth cutover.
Use cases include OLTP-like HBase workloads migrating to Cosmos DB for transactional workloads, and analytics-read patterns via Fabric mirroring.

Quick Start

Begin with a pilot migration of a representative subset to validate schema redesign, data movement, and cutover steps.

Frequently Asked Questions about azure-hdinsight-migration-hbase-to-fabric-cosmosdb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate HDInsight HBase workloads to Cosmos DB end to end?▼

Migrating HDInsight HBase to Cosmos DB requires schema redesign, partition-key translation, RU/s sizing, bulk export, client SDK rewrites, security mapping, dual-write cutover, and validation to minimize downtime.

What is the best way to translate HBase row keys to Cosmos DB partition keys?▼

Translating HBase row keys to Cosmos DB partition keys requires schema redesign to map column-family structures to JSON or wide-column formats while optimizing RU/s sizing for transactional workloads.

Can I use Fabric mirroring for analytics during Cosmos DB migration cutover?▼

Fabric mirroring supports analytics-read patterns and verification during cutover when migrating HBase workloads to Cosmos DB, enabling continuous validation of transactional data across both NoSQL and Cassandra APIs.

Does the HBase to Cosmos DB migration support both NoSQL and Cassandra APIs?▼

The migration supports both Cosmos DB NoSQL and Cassandra APIs, providing schema redesign and client SDK rewrite guidance tailored to each API model for HBase workload transitions.

How do I validate a pilot HBase to Cosmos DB migration before full cutover?▼

Validate a pilot migration by testing a representative subset of HBase data to confirm schema redesign, bulk data movement, RU/s sizing, and dual-write cutover steps before executing the full workload transition.

What are the limitations of dual-write cutover when migrating HBase to Cosmos DB?▼

Dual-write cutover limitations during HBase to Cosmos DB migration include client SDK rewrite complexity, security mapping alignment overhead, and the need for rigorous validation to prevent data inconsistency across transactional workloads.