Data, Files, and Connectors¶
These SDK resources manage Catalog assets and import local files into Tables or Volumes. The complete product data path is:
External source → Connector → Import task → Catalog
├─ Table (structured data)
└─ Volume / File (unstructured data)
Catalog → Export task → External destination
The official repositories are moi-python-sdk and moi-go-sdk. Both provide a low-level RawClient; Python also provides an SDKClient that wraps common import workflows.
Choose the resource by outcome¶
Outcome |
Start with |
Read |
|---|---|---|
Browse or manage structured assets |
Catalog, Database, Table |
|
Upload, list, download, or delete files |
Volume, Folder, File |
|
Stage and preview Connector files |
Connector File |
|
Import local files into Catalog |
Connector File + Import Task |
|
Understand the unsupported general export boundary |
Export Task |
|
Understand the unavailable sharing automation boundary |
Publication, Subscription |
Boundaries to establish first¶
Follow the installed version. Python low-level methods accept dictionaries; Go uses typed requests. Before upgrading, compare the installed API reference and public types with the target service version.
Use names for display and IDs for relationships. Persist the ID returned at creation time. Do not rediscover resources by name when building tasks, parent-child relationships, or delete requests.
Structured and unstructured data have different targets. Record-oriented data belongs in a Table; documents, images, audio, and video belong in a Volume. A filename extension alone is not enough to choose the target.
A successful request is not a completed asynchronous task. File-import responses contain a task ID. Persist it, read state with
get_task/GetTask, and inspect the destination after a terminal state.Check downstream use before deletion. Tables, Volumes, Folders, and Files may be referenced by workflows, knowledge bases, or tasks. Read reference lists before issuing destructive calls.
The current SDKs expose no public methods for external Connector configuration management, general Export Tasks, or Data Share. The corresponding pages state those boundaries explicitly; do not construct undocumented endpoints.