Specifies the name of the table. Should only contain alpha-numeric characters, hyphens (‘-‘), or underscores (‘’). (Using a double-underscore (‘_’) is not allowed and reserved for other features within Pinot)
Defines the table type -
Boolean field to indicate whether the table is a dimension table.
This section defines properties related to quotas, such as storage quota and query quota. For more details scroll down to quota.
This section defines the enabled minion tasks for the table. See Minion for more details.
This section defines the properties related to configuring how the broker selects the servers to route, and how segments can be pruned by the broker based on segment metadata. For more details, scroll down to routing.
This section defines the properties related to query execution. For more details scroll down to query.
This section defines the properties related to the segments of the table, such as segment push frequency, type, retention, schema, time column etc. For more details scroll down to segmentsConfig.
This section defines the indexing related information for the Pinot table. For more details head over to Table indexing config.
This section specifies the columns and the type of indices to be created on those columns. Currently, only Text search columns can be specified using this property. We will be migrating the rest of the indices to this field in future releases. See Field config list for sub-properties.
Define the server and broker tenant used for this table. More details about tenant can be found in Tenant.
This section defines the configs needed for ingestion level transformations. More details in Ingestion Level Transformations.
This section defines the configs related to the upsert feature.
This section defines configs needed to setup tiered storage. More details in Tiered Storage.
This section is for keeping custom configs, which are expressed as key-value pairs.
The following properties can be nested inside the top-level configs.
The maximum storage space the table is allowed to use, before replication. For example, in the above table, the storage is 140G and replication is 3. Therefore, the maximum storage the table is allowed to use is 140*3=420G. The space used by the table is calculated by adding up the sizes of all segments from every server hosting this table. Once this limit is reached, offline segment push throws a
The maximum queries per second allowed to execute on this table. If query volume exceeds this, a