Datastore migrations mismatch with the Trino cluster resource manager db

[michael-layfer]

Using the latest version 14 of Trino Gateway the flyway migration creates a single migration based on this: V1__create_schema.

Which breaks the Trino cluster resource manager db migrations - casuing the Trino clsuter to fail on start.

Workaround:

1. Start Trino cluster first, letting it apply its migrations on the shared resource manager db.
2. Create the missing Trino GW tables:

CREATE TABLE IF NOT EXISTS gateway_backend (
name VARCHAR(256) PRIMARY KEY,
routing_group VARCHAR (256),
backend_url VARCHAR (256),
external_url VARCHAR (256),
active BOOLEAN
);

CREATE TABLE IF NOT EXISTS query_history (
query_id VARCHAR(256) PRIMARY KEY,
query_text VARCHAR (256),
created bigint,
backend_url VARCHAR (256),
user_name VARCHAR(256),
source VARCHAR(256)
);
CREATE INDEX IF NOT EXISTS query_history_created_idx ON query_history(created);

3. Configure Trino GW to skip migration run:
   runMigrationsEnabled: false
4. Start Trino GW

[willmostly]

Do you use the resource group functionality in the Trino Gateway? We were considering it for removal, so it would be good to know if it is being actively used

[PiotrKurnik]

I think that it makes sense to keep it. That way you would have a single interface to control resource groups for all of the clusters. IMHO it's handy. Can you share the reasoning behind dropping it?

[PiotrKurnik]

OK, I found the summary of the contributors meeting. 👁
https://github.com/trinodb/trino-gateway/wiki/Contributor-meetings#trino-gateway-dev-sync-19th-mar-2025

[michael-layfer]

Yes I am using it to allow a single place managing all clusters resource groups

[willmostly]

see trinodb/trino#25451 (comment)

[mosabua]

Related to #656