hasura/graphql-engine v1.3.0-beta.1

on GitHub

Changelog

This is the first beta for v1.3. The highlights of this release are:

Data federation via Remote Joins

Remote Joins extends the concept of joining data across tables, to being able to join data across any compatible data source. This enables complete data federation as your sources can evolve independently while Hasura does the join, authorization and checks consistency of the unified schema.

In this release, you can create relationships from tables to remote schemas. This works similar to table relationships. Head to the Relationship tab in your table page and define a remote relationship:

• give a name for the relationship
• select the remote schema
• give the join configuration from table columns to remote schema fields.

The join configuration can refer to any field in the remote schema that takes an input argument and it can also take static values.

Once this is done, head to GraphiQL and make your query with the remote relationship! Note: Action relationships are kind of a reverse join of this where you can create a relationship from your action type to a table.

(#2392)

Relay

The Hasura GraphQL Engine now serves a Relay schema for Postgres tables which have a primary key defined.

The Relay schema can be accessed through /v1/relay endpoint.

(#4458)

Scheduled Triggers

A scheduled trigger can be used to execute custom business logic based on time. There are two types of timing events: cron based or timestamp based. Head to the Events page on the console and check it out.

A cron trigger will be useful when something needs to be done periodically. For example, you can create a cron trigger to generate an end-of-day sales report every weekday at 10 pm.

You can also schedule one-off events based on a timestamp. For example, a new scheduled event can be created for 2 weeks from when a user signs up to send them a reminder email (note: this would perhaps be done using the metadata API in your code).

(#3553, #4732)

Allow access to session variables by computed fields (fix #3846)

Sometimes it is useful for computed fields to have access to the Hasura session variables directly. For example, suppose you want to fetch some articles but also get related user info, say likedByMe. Now, you can define a function like:

CREATE OR REPLACE FUNCTION article_liked(article_row article, hasura_session json)
RETURNS boolean AS $$
  SELECT EXISTS (
    SELECT 1
    FROM liked_article A
    WHERE A.user_id = hasura_session ->> 'x-hasura-user-id' AND A.article_id = article_row.id
  );
$$ LANGUAGE sql STABLE;

and make a query like:

query {
  articles {
    title
    content
    likedByMe
  }
}

Support for this is now added through the add_computed_field API.

Read more about the session argument for computed fields in the docs.

Bug fixes and improvements

• server: fix explain queries with role permissions (fix #4816)
• server: compile with GHC 8.10.1, closing a space leak with subscriptions. (close #4517) (#3388)
• server: fixes an issue where introspection queries with variables would fail because of caching (fix #4547)
• server: avoid loss of precision when passing values in scientific notation (fix #4733)
• server: fix mishandling of GeoJSON inputs in subscriptions (fix #3239)
• server: fix importing of allow list query from metadata (fix #4687)
• server: flush log buffer during shutdown (#4800)
• server: fix edge case with printing logs on startup failure (fix #4772)
• console: allow entering big int values in the console (close #3667) (#4775)
• console: add support for subscriptions analyze in API explorer (close #2541) (#2541)
• console: avoid count queries for large tables (#4692)
• console: add read replica support section to pro popup (#4118)
• console: fix regression in editing permissions manually (fix #4683) (#4826)
• console: allow modifying default value for PK (fix #4075) (#4679)
• console: fix checkbox for forwarding client headers in actions (#4595)
• console: re-enable foreign tables to be listed as views (fix #4714) (#4742)
• console: display rows limit in permissions editor if set to zero (fix #4559)
• console: fix inconsistency between selected rows state and displayed rows (fix #4654) (#4673)
• console: fix displaying boolean values in Edit Row tab (#4682)
• console: fix underscores not being displayed on raw sql page (close #4754) (#4799)
• console: fix visiting view modify page overwriting raw sql content (fix #4798) (#4810)
• console: add help button and move about page to settings (#4848)
• console: add new sidebar icon that separates enums from tables (fix #4984) (#4992)
• cli: list all available commands in root command help (fix #4623) (#4628)
• cli: fix bug with squashing event triggers (close #4883)
• cli: add support for skipping execution while generating migrations through the migrate REST API
• cli: add dry run flag in hasura migrate apply command (fix #3128) (#3499)
• cli: load assets from server when HASURA_GRAPHQL_CONSOLE_ASSETS_DIR is set (close #3382)
• docs: add section on actions vs. remote schemas to actions documentation (#4284)
• docs: fix wrong info about excluding scheme in CORS config (#4685)
• docs: add single object mutations docs (close #4622) (#4625)
• docs: add docs page on query performance (close #2316) (#3693)
• docs: add a sample Caddyfile for Caddy 2 in enable-https section (#4710)
• docs: add disabling dev mode to production checklist (#4715)
• docs: add integration guide for AWS Cognito (#4822, #4843)
• docs: update troubleshooting section with reference on debugging errors (close #4052) (#4825)
• docs: add page for procuring custom docker images and binaries (#4828)
• docs: add content on how to secure action handlers and other actions docs improvements (#4743)
• docs: make header common with other hasura.io/ pages (#4957)
• install manifests: update all install manifests to enable dev mode by default (close #4599) (#4716)

Using this release

Use the following docker image:

hasura/graphql-engine:v1.3.0-beta.1