The release train continues towards the station (note: the station is named ‘Stable’) with the release of 2.0 alpha 10.
While ‘alpha’ in name, it is not alpha in quality. However, we do use this signifier to denote that it is a work in progress and invite feedback about any problems you may experience.
As mentioned in recent release posts, we have historically announced our releases via Discord and updates to the GitHub release page. As adoption continues to increase, we believe this is insufficient for the future.
To that end, we will begin to blog for each release (even if it is only small) so that you can track releases via blog, twitter (@HasuraHQ), Discord, and the Github Release page. In these posts, we will highlight a few specific elements of each release, but the exhaustive list of features and improvements is always in the changelog.
Overview
server: aggregation fields are now supported on mssql We are delighted to bring aggregate fields to MS SQL Server.
If you aren’t familiar, the ability to fetch aggregations on columns (along with nodes) is the outcome of using a Hasura aggregation query. The name of the aggregate field is <field-name> + _aggregate. Common functions include count, sum, avg, max, min, etc.
BigQuery support While, strictly, released in alpha 9 we neglected to highlight the arrival of Google BigQuery support in Hasura. All features are not, yet, available but we will continue to iterate. Postgres, SQL Server, and now Big Query all served via Hasura!
And more Those are, of course, just the highlights. All other fixes are included in the changelog.
Conclusion
Please use the docker target `hasura/graphql-engine:v2.0.0-alpha.10`, try it out, let us know what works and what needs improvement. You can find us on Twitter (@HasuraHQ) and in Github. For ad-hoc conversation, feel free to join us on the Hasura Community Discord.
And, if you want to get started now with the latest stable release, check out the deployment simplicity of Hasura Cloud.
Previous Posts
For previous release announcements in the 2.x series, please review: