Organizations
Every Hydrolix cluster includes at least one organization object which contains a hierarchy of projects and tables.
Using organizations⚓︎
Prior to Hydrolix v6.1, there was no support for multiple organizations. All projects and tables an a cluster existed underneath a single organization, automatically created at cluster installation time. The project and table hierarchy belonged to a single Org object.
Hydrolix v6.1 introduces a second hierarchy, defined using the Customer model.
This second hierarchy will replace the original hierarchy with a more flexible multi-Org hierarchy in a future release. At that time, the Customer objects will be promoted to Org objects to provide support for multiple organizations.
Transition to new hierarchy⚓︎
The transition allows incremental introduction for dependent software. For example, query and ingestion systems can switch gradually to the new hierarchy over several releases.
The left diagram depicted on this page is the only model supported as of Hydrolix v6.0.
See Org transition planning for a detailed description of the process, the changes, and planning guidance.
erDiagram
BGlobal["Global"]
BOrg[Org]
BProject[Project]
BTable[Table]
BGlobal ||--|| BOrg : contains-one
BOrg ||--o{ BProject : can-contain-multiple
BProject ||--o{ BTable : can-contain-multiple
DGlobal[Global]
DOrg[Org]
DCustomer[Customer]
DProject[Project]
DTable[Table]
DGlobal ||--o{ DOrg : contains-one
DGlobal ||--o{ DCustomer : can-contain-multiple
DOrg ||--o{ DProject : can-contain-multiple
DCustomer ||--o{ DProject : can-contain-multiple
DProject ||--o{ DTable : can-contain-multiple
AGlobal[Global]
AOrg["Org (was Customer)"]
AProject[Project]
ATable[Table]
AGlobal ||--o{ AOrg : can-contain-multiple
AOrg ||--o{ AProject : can-contain-multiple
AProject ||--o{ ATable : can-contain-multiple