Limits
Datastrato Enterprise and Apache Gravitino apply three kinds of limit. A system limit is enforced by the server and cannot be exceeded. A recommended limit marks the point beyond which performance or memory use starts to degrade. A source-defined limit belongs to the system a catalog federates, and that system's documentation is authoritative. Where Gravitino and a federated source both limit the same thing, the lower of the two applies.
Names and metadata
Names are checked by the server when an object is created. Comment and property sizes are set by the metadata database, so they depend on which database the install uses; PostgreSQL is the chart default. A catalog for a source system applies that system's own name rule in place of the 64-character default.
| Item | Limit | Limit type |
|---|---|---|
| Name length (metalake, catalog) | 64 characters | System |
| Name length (schema, table, view, column, fileset, topic, model, function) | 64 characters | System |
| Name length (tag, policy, role, user, group, job template, statistic) | 128 characters | System |
| Comment length (metalake, catalog, schema, column, fileset, topic, tag) | 256 characters | System |
| Comment length (table) | 16 MB on MySQL, 1 GB on PostgreSQL | System |
| Comment length (view, function, policy, job template) | 64 KB on MySQL, 1 GB on PostgreSQL | System |
| Comment length (model, model version) | 64 KB on MySQL, 65,535 characters on PostgreSQL | System |
| Serialized properties per object | 16 MB on MySQL, 1 GB on PostgreSQL | System |
| Object name length on PostgreSQL sources | 63 characters | Source-defined |
| Object name length on MySQL sources | 64 characters | Source-defined |
| Object name length on SQL Server sources | 128 characters | Source-defined |
| Object name length on Oracle sources | 128 bytes (30 bytes before 12.2) | Source-defined |
Catalogs and objects
| Item | Limit | Limit type |
|---|---|---|
| Catalogs per server (default memory settings) | 50 | Recommended |
| Oracle catalogs with distinct connections per server (default memory settings) | 30 | Recommended |
| JDBC and Iceberg JDBC catalogs per PostgreSQL source | 55 | Recommended |
| Schemas per catalog | 1,000 | Recommended |
| Tables or filesets per schema | 10,000 | Recommended |
| Topics or models per schema | 5,000 | Recommended |
| Views per schema | 500 | Recommended |
| Versions per model | 1,000 | Recommended |
| Leaf columns in a table | 4,000 | Recommended |
| Job templates per metalake | 500 | Recommended |
Governance and access control
| Item | Limit | Limit type |
|---|---|---|
| Tags per metalake | 5,000 | Recommended |
| Tags per object | 50 | Recommended |
| Policies per metalake | 1,000 | Recommended |
| Policies per object | 20 | Recommended |
| Users per metalake | 10,000 | Recommended |
| Groups per metalake | 500 | Recommended |
| Roles per metalake | 200 | Recommended |
| Roles per user | 20 | Recommended |
| Groups per user | 10 | Recommended |
| Users per group | 500 | Recommended |
| Securable objects per role | 20 | Recommended |