v2.39.0-beta.1

Changelog

Bug fixes and improvements

Server

• The server now logs timing information on error when possible, e.g. when an SQL query fails.
• Generate an info message instead of a warning when the GC is forced to run.
• Add operation_name and parameterized_query_hash labels to the hasura_graphql_requests_total Prometheus metric. (Cloud / Enterprise edition only)
• Support env variable template to set the OpenTelemetry status (fix #10177) (Cloud / Enterprise edition only)

Console

• Fix values not being suggested in dropdowns of the permissions builder if only 1 option exists

v2.38.1

Changelog

This is a patch release for v2.38

Bug fixes and improvements

Build

• Update the Red Hat UBI base images to receive latest security updates

v2.38.0

Changelog

Behaviour changes

• Add automatic quoting to Native Query parameters for Snowflake. (Cloud / Enterprise edition only)

  Note that this may affect existing Native Queries in contexts where query authors have manually added quotes around parameter injection sites; removing the manual quotes should resolve this issue.

Bug fixes and improvements

Server

• Add the ability to force refresh of dynamic db connection strings. (Cloud / Enterprise edition only)

  When the HASURA_SECRETS_BLOCKING_FORCE_REFRESH_URL env var is defined, then on retry Hasura will post this payload to the URL:

  {"filename": <path>}
  

  Crucially it is assumed that the Hasura server only returns after the referenced secret file has been updated.

• Ignore dynamic headers x-real-ip, x-forwarded-for, true-client-ip while generating cache keys. (Cloud / Enterprise edition only)

Console

• Fix console crash when using Native Queries in an array relationship.
• Add ClickHouse and Trino database logos. Fix an issue where some logos may not have been displaying correctly for data-connector backed databases.

Data Connectors

• In the JVM connection pool, validate connections when borrowing them. This prevents the issue where, for example, the DB server is terminated and the pool is unaware that the connection is in an invalid state, leading to errors.
• Inline query parameters in output generated by the GraphiQL Analyze button (i.e. the Explain API). Also, use dialect-specific SQL based on the current connector rather than a default/generic dialect.

v2.38.0-beta.1

Changelog

Bug fixes and improvements

Server

• Ignore dynamic headers x-real-ip, x-forwarded-for, true-client-ip while generating cache keys. (Cloud / Enterprise edition only)

Console

• Fix console crash when using Native Queries in an array relationship.
• Add ClickHouse and Trino database logos. Fix an issue where some logos may not have been displaying correctly for data-connector backed databases.

Data Connectors

• Inline query parameters in output generated by the GraphiQL Analyze button (i.e. the Explain API). Also, use dialect-specific SQL based on the current connector rather than a default/generic dialect.

v2.37.1

Changelog

This is a patch release for v2.37

Bug fixes and improvements

Server

• Fix output of error field for asynchronous actions with 2xx response status.

Data connectors

• Remove explicit NULL ordering when generating ORDER BY statements.
  Some dialects such as MySQL do not support ORDER BY ... NULLS FIRST/LAST
  The translation to ORDER BY CASE WHEN causes the optimizer to be unable to use indices.

v2.37.0

Changelog

Bug fixes and improvements

Server

• When adding a data connector agent, the agent URI can now be sourced from an environment variable (fix #9777).
• Allow ignoring the errors field if both data and errors are present in the Remote Schema response. Can be configured via the server HASURA_GRAPHQL_REMOTE_SCHEMA_PRIORITIZE_DATA env var or the remote-schema-prioritize-data flag.
• Remove additional internal error response field being returned in Async Actions when dev mode is false.
• Ensure Logical Models do not create empty GraphQL object types.
• Add a new environment variable HASURA_GRAPHQL_CONFIGURED_HEADER_PRECEDENCE to specify header precedence when delivering payload to webhook in actions and input validations.
• BigQuery filters now support ilike and nilike for case-insensitive versions of like and nlike.

Console

• Also prettify the query variables on hitting the GraphiQL Prettify button (fix #9968).
• Sort the columns in the filter and sort column selectors alphabetically in the data browser (fix #9966).
• Show table schema names in the new relationships UI for PostgreSQL and MS SQL Server.

Data Connectors

• Fix multi-schema issue for simple queries in Snowflake. (Cloud / Enterprise edition only)
• Fix aggregation limit for Snowflake, now aggregate limits are treated separately from row-based limits which can come through from permission-based limits. (Cloud / Enterprise edition only)
• Add support for the following additional JDBC auth mechanisms: (Cloud / Enterprise edition only)
  • AWS
    • password managed by the AWS Secrets Manager
    • IAM based access for AWS (available for MySQL, MariaDB and PostgreSQL)
  • Snowflake
    • encrypted private keys

Build

• Update the Ubuntu and Red Hat UBI base images to receive latest security updates

v2.36.3

Changelog

This is a patch release for v2.36

Bug fixes and improvements

Server

• Fix query caching when database connection templates are involved. Session variables and HTTP headers used in the templates are now included in the cache key generation. (Cloud / Enterprise edition only)

v2.37.0-beta.1

Changelog

Bug fixes and improvements

Server

• When adding a data connector agent, the agent URI can now be sourced from an environment variable (fix #9777).
• Allow ignoring the errors field if both data and errors are present in the Remote Schema response. Can be configured via the server HASURA_GRAPHQL_REMOTE_SCHEMA_PRIORITIZE_DATA env var or the remote-schema-prioritize-data flag.
• Remove additional internal error response field being returned in Async Actions when dev mode is false.
• Ensure Logical Models do not create empty GraphQL object types.

Console

• Also prettify the query variables on hitting the GraphiQL Prettify button (fix #9968).
• Sort the columns in the filter and sort column selectors alphabetically in the data browser (fix #9966).

Data Connectors

• Fix multi-schema issue for simple queries in Snowflake. (Cloud / Enterprise edition only)
• Fix aggregation limit for Snowflake, now aggregate limits are treated separately from row-based limits which can come through from permission-based limits. (Cloud / Enterprise edition only)

Build

• Update the ubuntu and redhat ubi base images to receive latest security updates

v2.36.2

Changelog

This is a patch release for v2.36

Bug fixes and improvements

Server

• Support SpanKind for OpenTelemetry traces (Cloud / Enterprise edition only)

Console

• Add permission summary view for data-connector based databases.
• Fix issues with permission summary on the new Data tab UI.

v3.alpha.12-19-2023 Release 🚀

We're thrilled to announce the alpha release of Hasura V3! 🎉

Key Features

• Data Connectors: The v3-engine can be used with any connector that adheres to the NDC specification to get a GraphQL API. We currently have NDC agents available for Postgres, Clickhouse and Deno (Typescript). Learn more about Hasura connectors here.
• Metadata Modeling Objects: Use these metadata objects to map the underlying data sources using NDC agents and create a supergraph:
  • Models: collections of data objects that can be queried. These serve as the interface for querying your data. A model may be backed by a database table, an ad-hoc SQL query, a pre-materialized view or a custom API server.
  • Commands: opaque functions or procedures that can be used to query or mutate data. You can use them to validate, process, enrich some data or call another API,
  • Permissions: access control rules on your types / models / commands. There are two types of permissions available - model permissions and type permissions.
  • Relationships: creating edges in your graph from a data type to a model or a command. A relationship allows you to query nested or linked information and it can span across multiple data sources such as from Postgres to Clickhouse.
  • Global ID: is a unique identifier for an object across the entire application, not just within a specific table or type.The Global ID generated by Hasura DDN follows the Relay Global ID spec and can be used to fetch any object directly.
• GraphQL API Features
  • Queries - Leverage a powerful API to query data with the following features -
    • Simple Queries including query by primary key, running multiple queries in a request, using multiple arguments in the same query, using variables, aliases and fragments.
    • Nested Queries including object and array relationships across data sources.
    • Sorting objects, nested objects, sorting based on nested object’s fields including computed fields, and sorting by multiple fields.
    • Pagination using limit and offset operators including limiting results from an offset, limiting results in a nested object and keyset cursor based
    • Filtering using the where argument with support of the following operators - simple comparison operator, boolean operator, text search operator and nested objects.
    • Directives including @include and @skip for fields.
    • Native Queries for PostgreSQL where each query is specified as SQL and can take arguments using the {{argument_name}} syntax
    • Business Logic - Now write your business logic in Typescript and use Hasura to front them as queries and mutations using the Typescript Deno connector.
  • Mutations - Leverage the flexibility of mutating data with the following ways -
    • Using the Typescript Deno connector which exposes Typescript functions as Hasura commands, which can be made available over the GraphQL API as a mutation. You can write to a database or an API and incorporate any business logic in the Typescript function while mutating.
    • Point to point (simple) database inserts, updates, and deletes via the respective data connectors are coming soon.
• Authentication: Hasura v3 utilizes "session variables", with specific user, role, organization and any other information you may need to determine the data access rights of the user. Hasura's authentication can be configured via JSON web tokens (JWT) or a webhook service and can be integrated with any other provider you choose.

Alpha Phase

This release marks the initial phase of our alpha rollout. Please note that Hasura V3 is still in its early stages and has limited functionality. We encourage feedback, bug reports, and contributions from the community to help us shape the future of this project.

Get Involved

We're excited to have you on board as we embark on this journey together.

• Report any bugs or issues you encounter via GitHub Issues.
• Propose new features or enhancements via Pull Requests.
• Join the discussions in our Discord channel.

Your participation and feedback are invaluable as we work towards more updates and exciting features in the upcoming releases! 🚀