79: Going for 1.0.0

Introduction

Jan Waś and João Folgado join Manfred Moser to talk more about the amazing work on the trino-go-client that led to the recent 1.0.0 release. We learn about the rich feature set, collaborators, how we got here, performance, and next steps.

Video

• Introduction with Manfred (0.0s)
• Release updates for Trino 480, 481, 482, and 483 (62.0s)
• Trino Gateway releases 17 to 21 (275.0s)
• trino-js-client 1.0.0 and trino-query-ui (308.0s)
• Trino contributor calls and the Grafana plugin (393.0s)
• Introducing Jan and João (448.0s)
• History of the trino-go-client (768.0s)
• Feature parity with the JDBC driver, transactions, and database/sql (871.0s)
• Declaring 1.0.0 and the JDBC driver as reference (1033.0s)
• Spooling protocol explained (1167.0s)
• Implementing the spooling protocol with goroutines (1615.0s)
• Production use with the direct protocol (1824.0s)
• Mapping Trino data types to Go (1896.0s)
• Trino data types and connector type mapping (2161.0s)
• Binding Go slices and maps as parameters (2294.0s)
• Breaking changes and upgrading through 0.338.0 to 1.0.0 (2389.0s)
• Releases 1.1.0 and 1.2.0, and the usql project (2605.0s)
• AI tooling for maintainers and contributors (2888.0s)
• Demo of nested data types with generics (3368.0s)
• Go modules and Go version upgrades (3758.0s)
• Demo of the variant type (3940.0s)
• Demo of time zone fixes (4236.0s)
• Demo of transactions (4400.0s)
• Demo of performance with JSON v2 (4628.0s)
• OAuth 2.0 and Kerberos authentication (4925.0s)
• What's next for Jan and João (5074.0s)
• Rounding out with upcoming events (5173.0s)

Host

• Manfred Moser, Sr. Principal DevRel Engineer at Chainguard, open source hacker at simpligility

Guest

• Jan Waś, Software Engineer at IceGuard
• João Folgado, Software Engineer at ABC Fitness

Releases and news

Following are highlights and selections from the releases since episode 78. Check the full release notes for details.

Trino 480

• Add the number data type.
• Add the DataSketches functions.
• Allow query parameters in the FOR VERSION AS OF and FOR TIMESTAMP AS OF clauses.
• Add cluster status information to the header of the preview Web UI.
• Improve performance of remote data exchanges and aggregations.

Trino 481

• Add support for the NEAREST clause for approximate matches in joins.
• Add support for the variant type to the JDBC driver and the CLI.
• Add support for persisting external authentication tokens across JDBC client processes.
• Replace the Esri geometry library with JTS.
• Remove legacy object storage support for Azure Storage.

Trino 482

• Add support for named arguments in function calls.
• Add support for the AT LOCAL operator, and the MATCH and UNIQUE predicates.
• Add the ends_with and OVERLAY string functions.
• Add buttons to cancel or preempt a running query to the preview Web UI.
• Remove support for the Alluxio file system.

Trino 483

• Add support for the PIVOT clause.
• Add support for the OVERLAPS predicate and the title_case function.
• Add numerous geospatial functions, including ST_Transform.
• Make the redesigned Web UI the default.
• Add support for themed, colorized output to the CLI.

As always, numerous performance improvements, bug fixes, and other features were added as well.

Other releases and news

• trino-go-client 1.0.0 released after the 0.334.0 to 0.338.0 releases in the preceding weeks
• Trino Gateway releases 17, 18, 19, 20, and 21, with 22 in the works
• trino-js-client 1.0.0 is released and ready for use
• trino-query-ui 2.0.0 is available as a React component for your own applications
• grafana-trino is moving fast with end-to-end tests and regular releases
• Trino Contributor Call minutes are available:
  • January 2026
  • February 2026
  • March 2026
  • April 2026
  • May 2026
  • June 2026
  • July 2026
  • August 2026
  • September 2026

Introducing Jan and João

Jan tells us how he started with Trino at Starburst, and how his pull requests for the Go client led to him becoming its maintainer. He also maintains the Helm charts and the Grafana plugin.

João is a senior software engineer at ABC Fitness in Portugal, where his team uses Trino and Go for CRM workflows. A pull request to fix query cancellation was his start, followed by many more contributions to the Go client.

Going for 1.0.0

We talk about the history of the trino-go-client, which was forked from the original Presto driver, and the recent push for feature parity with the JDBC driver. A tracking issue from Sylwester Lachiewicz listed the gaps, and he addressed most of them. João added support for the number type and transactions through the standard database/sql interface.

Jan explains how the spooling protocol works and João tells us how they implemented it with a pipeline of goroutines for fetching, downloading and decoding segments in parallel, while keeping the results in order and memory usage bounded.

We also discuss mapping the Trino data types to Go types, binding Go slices and maps as query parameters, and the breaking changes in 1.0.0. The new generic scanners replace the hand-written slice and map types, and 0.338.0 is the recommended stepping stone for upgrades. Since then, 1.1.0 added the remaining data types, including intervals, and 1.2.0 uses the new JSON v2 package and requires Go 1.27.

We chat about how AI tooling helps maintainers and contributors with gap analysis, reviews, and the tasks nobody wants to do. Jan then demos nested data types with generics, the variant type, time zone fixes, transactions, and the lower memory usage with JSON v2. He also covers OAuth 2.0 and Kerberos credential cache support.

Resources

• trino-go-client
• trino-go-client releases
• Feature parity tracking issue
• Trino data types
• usql, the universal command line interface for SQL databases
• Trino users, now including OpenAI, Datadog, and Blinkit

Rounding out

• 28 Oct 2026 - Trino Contributor Call
• Looking for guests and topics for Trino Community Broadcast 80 and beyond