Skip to main content

Glossary

Infinite Data product terms explained in plain language for querying, governance, auditing, and administration.

When to use this​

  • Use it when you come across a new term in the Console.
  • Use it to align communication between users, managers, auditors, and administrators.
  • Use it before opening access requests or asking for audit evidence.

Before you start​

  • Have the context in which the term appeared.
  • Check the related task page when you need step-by-step instructions.
  • Remember that names can vary with your organization's configuration.

Step by step​

  1. Catalog: the set of data available for discovery and governed querying.
  2. Schema: a grouping inside a catalog, usually related to a domain or system.
  3. Table: a queryable structure made of columns and rows.
  4. Column: a field in a table, such as a date, identifier, value, or status.
  5. Data rule: a grant defining who may query which data, for how long, and with which protections.
  6. Whole schema: a rule covering every table in a schema, including new tables where applicable.
  7. Specific tables: a rule covering only the tables you choose.
  8. Column mask: a protection hiding part or all of a sensitive column's value.
  9. Row filter: a protection limiting which records appear for a person, group, or account.
  10. Propagation: the short interval between saving a change and it taking effect everywhere.
  11. Service account: the identity used by automations and integrations.
  12. Audit Center: the area for searching actions, decisions, and evidence.
  13. Lineage: a view of who queried a table and when.
  14. NoteCore — the notebook area for analysis in Infinite Data.

What happens next​

  • You can use the same terms in requests, reviews, and investigations.
  • Access requests become clearer.
  • Audits become easier to explain.

Common errors​

  • Using terms the requester does not understand.
  • Confusing metadata visibility with authorization to query data.
  • Treating a group, a role, and a data rule as if they were the same thing.

Good practice​

  • Use full catalog, schema, and table names.
  • Explain the business purpose alongside the product term.
  • When in doubt, check the related task guide.

Next steps​