Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
The naming_convention experimental feature now also covers:
on_conflict upserts.Since these changes are breaking by nature, their use is gated by a feature flag, which can be enabled by setting the environment variable HASURA_FF_NAMING_CONVENTION_SEP_2023=True.
(partially fixes: #8929)
Add support for environment variable templating in OpenTelemetry endpoint URLs. (Cloud / Enterprise edition only)
Fix a memory leak in EE wherein data would accumulate in memory at each replace_metadata call. (Enterprise edition only)
Data Tab's Permissions section.Data tab.This is a patch release for v2.11
null value to a variable with a declared non-nullable type were previously allowed. Now, queries with this aforementioned condition will be properly invalidated and rejected.naming-convention GAThe naming-convention feature for PostgreSQL sources, previously in the experimental phase, is now generally available and fully enabled. Users can still specify HASURA_GRAPHQL_EXPERIMENTAL_FEATURES=naming_convention, although it is no longer necessary as it will have no impact and will eventually be removed.
Edit: Post this beta release, it was decided to leave this feature as experimental for the v2.34.0 stable release.
The naming_convention experimental feature now also covers:
on_conflict upserts.Since these changes are breaking by nature, their use is gated by a feature flag, which can be enabled by setting the environment variable HASURA_FF_NAMING_CONVENTION_SEP_2023=True.
(partially fixes: #8929)
Add support for environment variable templating in OpenTelemetry endpoint URLs. (Cloud / Enterprise edition only)
Fix a memory leak in EE wherein data would accumulate in memory at each replace_metadata call. (Enterprise edition only)
Data Tab's Permissions section.Data tab.This is a patch release for v2.33
We’re delighted to release the beta version of our ClickHouse data connector, which supports queries, table relationships, remote relationships, and permissions for ClickHouse.
For more information on how to set this up, please see our docs. This integration is built using Hasura Data Connectors.
Hasura now supports using remote source relationships in permission predicates. This means you can now define permission based on a column from a remote Postgres source.
Limitations
The remote relationship predicate must follow the following template:
{
"<rel name>": {
"<remote column name>": {
"<op>": "<some session variable name or some literal text>"
}
}
}
This implies the following:
_and, _or, _not or _exists node._eq, _neq, _gt, _lt, _gte, _lte, _in, _nin, _like, _nlike and _is_null operators are supported for comparing fieldsThe remote source relationship permission can only be defined for Postgres and data connector backends.
The remote source relationship RHS backend can be Postgres only.
Hasura now allows returning data in a table along with related data returned from a Native Query using a nested GraphQL query.
Hasura now supports creating Logical Models & Native Queries on Snowflake data sources.
error for Trigger failures in Hasura Cloud. Previously, the log level for Trigger errors was info. (Hasura Cloud only)
null valued variables with customized types were causing a GraphQL exception from the upstream server (fix #9757).HASURA_GRAPHQL_ENABLE_TRIGGERS_ERROR_LOG_LEVEL to set the log-level of Event Triggers failures to error. By default, the value is set to log-level Info. (Community / Enterprise edition only)
_contains and _contained_in operators for PostgreSQL arrays to be used with permissions.hasura_websocket_messages_sent_bytes_total. (Cloud / Enterprise edition only)
hasura_postgres_connection_init_time and hasura_postgres_pool_wait_time. (Cloud / Enterprise edition only)
hasura_otel_sent_spans and hasura_otel_dropped_spans. (Cloud / Enterprise edition only)
bulk responses.- in their names.string for tables of Data-connector backed data sources.We’re delighted to release the beta version of our ClickHouse data connector, which supports queries, table relationships, remote relationships, and permissions for ClickHouse.
For more information on how to set this up, please see our docs. This integration is built using Hasura Data Connectors.
Hasura now supports using remote source relationships in permission predicates. This means you can now define permission based on a column from a remote Postgres source.
Limitations
The remote relationship predicate must follow the following template:
{
"<rel name>": {
"<remote column name>": {
"<op>": "<some session variable name or some literal text>"
}
}
}
This implies the following:
_and, _or, _not or _exists node._eq, _neq, _gt, _lt, _gte, _lte, _in, _nin, _like, _nlike and _is_null operators are supported for comparing fieldsThe remote source relationship permission can only be defined for Postgres and data connector backends.
The remote source relationship RHS backend can be Postgres only.
Hasura now allows returning data in a table along with related data returned from a Native Query using a nested GraphQL query.
Hasura now supports creating Logical Models & Native Queries on Snowflake data sources.
null valued variables with customized types were causing a GraphQL exception from the upstream server (fix #9757)._contains and _contained_in operators for PostgreSQL arrays to be used with permissions.hasura_websocket_messages_sent_bytes_total. (Cloud / Enterprise edition only)
hasura_postgres_connection_init_time and hasura_postgres_pool_wait_time. (Cloud / Enterprise edition only)
hasura_otel_sent_spans and hasura_otel_dropped_spans. (Cloud / Enterprise edition only)
bulk responses.