System engine documentation
Firebolt’s system engine enables running various metadata-related queries without having to start an engine. The system engine is always available for you in all databases to select and use.
The system engine supports running the following commands:
SELECT CURRENT_TIMESTAMP()
Connect via the connector without specifying the engine_name. Database parameter is optional.
System engine does not need a database defined. If you wish to connect to an existing database and run metadata queries with the system engine, just specify the name of your database.
Example
Guidance on creating service accounts can be found in the service account section.
Any other Firebolt connector can also be used similarly, as long as the engine name is omitted.
System engine only supports running the metadata-related queries listed above. Additional queries will be supported in future versions.
To ensure fair and consistent access to the System Engine for all users, we have introduced rate limits that govern resource usage per account. These limits are designed to prevent resource contention and ensure optimal performance for everyone.
When the rate limits are exceeded on the system engine, the system will return the following error: 429: Account system engine resources usage limit exceeded
.
This error typically occurs when an account submits an excessive number of queries or executes highly complex queries that surpass the allocated resource thresholds.
What to Do If You Encounter Rate Limits
If you receive the 429 error, consider these steps to resolve the issue:
Best Practices to Avoid Rate Limits
Why This Matters
These rate limits are critical for maintaining a fair and robust environment where all users can achieve reliable performance without disruption from resource-heavy neighbors. This measure aligns with our commitment to delivering consistent and high-quality service across all accounts.
For additional support or questions, please contact our support team or refer to our documentation on optimizing query performance.
System engine documentation
Firebolt’s system engine enables running various metadata-related queries without having to start an engine. The system engine is always available for you in all databases to select and use.
The system engine supports running the following commands:
SELECT CURRENT_TIMESTAMP()
Connect via the connector without specifying the engine_name. Database parameter is optional.
System engine does not need a database defined. If you wish to connect to an existing database and run metadata queries with the system engine, just specify the name of your database.
Example
Guidance on creating service accounts can be found in the service account section.
Any other Firebolt connector can also be used similarly, as long as the engine name is omitted.
System engine only supports running the metadata-related queries listed above. Additional queries will be supported in future versions.
To ensure fair and consistent access to the System Engine for all users, we have introduced rate limits that govern resource usage per account. These limits are designed to prevent resource contention and ensure optimal performance for everyone.
When the rate limits are exceeded on the system engine, the system will return the following error: 429: Account system engine resources usage limit exceeded
.
This error typically occurs when an account submits an excessive number of queries or executes highly complex queries that surpass the allocated resource thresholds.
What to Do If You Encounter Rate Limits
If you receive the 429 error, consider these steps to resolve the issue:
Best Practices to Avoid Rate Limits
Why This Matters
These rate limits are critical for maintaining a fair and robust environment where all users can achieve reliable performance without disruption from resource-heavy neighbors. This measure aligns with our commitment to delivering consistent and high-quality service across all accounts.
For additional support or questions, please contact our support team or refer to our documentation on optimizing query performance.