datahub-connector-planning

To plan a DataHub connector, you need to classify the source system, gather requirements, and design the architecture. This Skill guides you through this workflow to generate a detailed `_PLANNING.md` blueprint covering entity mapping and base class selection.

Extracting metadata entities for DataHub connectors requires mapping source system attributes to DataHub standards. The Skill provides architecture and entity mapping guidance to help you define exactly which metadata structures to capture for SQL, API, or NoSQL sources.

Yes, DataHub connector planning supports SQL, API, and NoSQL sources. The workflow leverages DataHub reference documents and standards to guide the classification and requirements gathering for these specific source system types.

Selecting the right base class for a DataHub connector involves matching your source system characteristics with DataHub architecture standards. The Skill provides clear guidance on base class selection and configuration design based on official reference documents.

The best way to document DataHub connector requirements is to generate a comprehensive `_PLANNING.md` blueprint. This Skill facilitates source system research and requirements gathering to produce this detailed architectural document before implementation begins.

A planning document is needed before developing a DataHub ingestion connector to ensure robust and well-documented implementations. It streamlines the complex design process by defining architecture, entity mapping, and configuration requirements upfront.