Support high version Trino

[hqbhoho]

New version Trino, Some ConnectorMetadata API will change. eg:
In Trino 440

    /**
     * Finish insert query
     */
    default Optional<ConnectorOutputMetadata> finishInsert(
            ConnectorSession session,
            ConnectorInsertTableHandle insertHandle,
            List<ConnectorTableHandle> sourceTableHandles,
            Collection<Slice> fragments,
            Collection<ComputedStatistics> computedStatistics)
    {
        throw new TrinoException(GENERIC_INTERNAL_ERROR, "ConnectorMetadata beginInsert() is implemented without finishInsert()");
    }

but in 435

    /**
     * Finish insert query
     */
    default Optional<ConnectorOutputMetadata> finishInsert(
    ConnectorSession session, 
    ConnectorInsertTableHandle insertHandle, 
    Collection<Slice> fragments, 
    Collection<ComputedStatistics> computedStatistics)
    {
        throw new TrinoException(GENERIC_INTERNAL_ERROR, "ConnectorMetadata beginInsert() is implemented without finishInsert()");
    }

So some SQL will failed because of incompatible API. 435 is one year ago version.

[hqbhoho]

@diqiu50 cc

[diqiu50]

Yes, it’s time to upgrade the supported Trino version.

[hqbhoho]

Yes, it’s time to upgrade the supported Trino version.

Maybe can we use create catalog xxxx using mysql rathar than create catalog xxxx using gravitino? Grivitino only provide catalog info. it can reduce depend on trino version.

[diqiu50]

With this approach, Gravitino cannot participate in the Trino query execution process, which makes it impossible to support certain advanced features.

[hqbhoho]

okk I see. Maybe data security and so on.

[hqbhoho]

I would like to do it if need! In our company, Trino mysql catalog are managed by Gravitino.

[shaofengshi]

• for upgrade the trino connector