Hasura - v2.17.0

Changelog

Highlights

New Action Type Generator to import types from Table

While creating a new Action, now you can use a new type generator "From Table" on the Console to easily create GraphQL types from generated type definitions.

This helps users to import one or more table types to the Action Type configuration that are already present in the GraphQL schema without having to manually enter them again.

This is a beta feature and we started an open discussion #9273 to track enhancement requests & feature level design discussions.

Revamped Cron Triggers page with Request Transforms added

The cron trigger form on the UI has been revamped to meet the design standards of the rest of the Hasura platform. Some improvements have been made such as adding the delete feature and adding request transform section to the form (see below).

CLI enhancements for database seeds

• add flag --all-databases to hasura seeds command to apply seeds on all databases
• add flag --with-seeds to hasura deploy command to also apply database seeds
• better handle case when no seeds are present for certain databases when applying seeds on all databases

Data Connectors Beta API

We are pleased to announce the Data Connectors beta API.

What are Data Connectors?

Data Connectors are microservice-based database drivers that extend Hasura's GraphQL Engine to support new backends.

For a detailed explanation of the feature, the best place to look is currently the
Data Connectors README.md.

The API currently supports:

• Queries
• Relationships
• Comparisons
• Aggregations
• Explain
• Prometheus Metrics
• Raw Queries
• User-Defined Scalar Types

and is being regularly extended with new features.

For more information, please see:

• The Data Connectors README.md
• The Data Connectors Directory on Github
• The dc-api-types NPM Package
• The Hasura Blog Data Connectors Announcement
• The Hasura Blog Athena Announcement

Bug fixes and improvements

Server

• Add new metadata API (<db_kind>_suggest_relationships) for suggesting relationships from the server for use by console and other clients.
• Fixes a bug with quoting database trigger names which might throw an error when creating event triggers on SQL Server
• Respect custom column name for graphql-default naming convention (fixes #9306)
• Fixed the edge case in multiplexed queries where a run-time SQL exception caused by a subscription query affects all subscriptions in the batch (fix #9281)
• Respect stringify-numeric-types option in remote database relationships (fix #8387)
• Fix the behavior of the clear_metadata and replace_metadata APIs when the metadata is inconsistent. Now, the APIs succeed and a log with the type metadata-log is emitted if the graphql-engine footprint is not cleared successfully. The following cases have been fixed:
• Source is inconsistent - source with name "<source-name>" is inconsistent
• Table is inconsistent and an event trigger is present - event trigger "<event-trigger-name>" does not exist.
• Postgres 10 is EOL since November 10, 2022 and so thus ends Hasura GraphQL engine's official support with it.
• Provide capability for Data Connector agents to map custom scalar types to built-in GraphQL types for parsing purposes.
• Fix a bug in the OpenTelemetry exporter where it would attempt to export spans when there were none, resulting in repeated log lines by the exporter even when the feature was disabled. (Enterprise edition only)
• Fix missing query-log log type for Enterprise Edition (Enterprise edition only)
• Add experimental Prometheus metrics for measuring approximations of the data transferred by HTTP requests, WebSocket messages, actions, event triggers, and scheduled triggers. These metrics may be removed at a later time. (Enterprise edition only)
• Add the hasura_event_processing_time_seconds Prometheus metric for better monitoring of event triggers (Enterprise edition only)
• Propagate B3 sampling state (X-B3-Sampled header) (Enterprise edition only)

Console

• Fixes an issue where creating an Asynchronous action actually created it as a Synchronous action. (fix #9286)
• Fixes an issue where Null comments on REST endpoints created by older Hasura versions prevent editing endpoint (fix #9347)
• Show notifications for console queries running longer than 10 seconds to help debug slow queries.
• Fix performance issue when displaying invocation logs of an event trigger.
• Minor enhancements to the one-off scheduled trigger form on the console. As a result of the change, placement of few fields have changed including that of comment/description.
• Fix issues with missing props - ssl_configuration, isolation_level and use_prepared_statements when creating/editing read-replicas.
• Fix Target Columns not found issue with the new Postgres relationship UI
• Add console support for AlloyDB
• View local relationships data for Amazon Athena and Snowflake tables from the Browse Rows section.
• Add a section on remote schema tabs to show remote schema inconsistency information.
• Fix console errors when data is not ready yet (fix #9238)
• Improve the performance for the data tab on read-only data fetch requests
• Fix miscellaneous issues when generating actions from OpenAPI. (Cloud / Enterprise edition only)

CLI

• Fix offline assets mode configuration not being respected by CLI console (fix #8482)
• Update log messages to surround database names with ''
• Adds support for metadata changes introduced by Data Connectors and also adds support for backend_configs root level object in metadata JSON.