Skip to main content
GuideServerConfigure and deploy Tabsdata servers on your machine.TutorialsConfigure data integration workflows within a running Tabsdata server.Advanced TutorialsBuild end-to-end workflows between two specific systems.API ReferenceCLI ReferenceRelease Notes
Version: 2.0.0

Create a Collection

create a collection called subscriptions for the billing transformers

Called tabsdata 2 times (ctrl+o to expand)

subscriptions is created in the default group, which makes it a data product collection: it holds transformers and carries no connection.

┌──────────────┬──────────────────────┐
│    field     │        value         │
├──────────────┼──────────────────────┤
│ name         │ subscriptions        │
├──────────────┼──────────────────────┤
│ description  │ Billing transformers │
├──────────────┼──────────────────────┤
│ project      │ finance              │
├──────────────┼──────────────────────┤
│ group        │ default              │
├──────────────┼──────────────────────┤
│ type         │ data product         │
├──────────────┼──────────────────────┤
│ connection   │ none                 │
├──────────────┼──────────────────────┤
│ storage path │ /                    │
└──────────────┴──────────────────────┘

Ask for a source or destination collection instead and I would need a connection document with it, because those are created with their connection rather than given one later. The group you name and the connection you pass have to agree, and a mismatch is an error rather than a silent choice.