I've noticed, Presto uses SQL transactions in metadata operations like getTables. Is it expected behavior?
My configuration:
Presto 0.278,
Presto JDBC driver 0.278,
SQL connection set with autoCommit = false,
Cassandra catalog.
In my Cassandra catalog, I have two keyspaces that have the same name but different case like:
quoted,
QuoteD.
When I run getTables(cassandra, quoted), I'm getting below error:
More than one keyspace has been found for the case insensitive schema name: quoted -> (QuoteD, quoted)
That's ok, but when I try to do the same operation I'm getting:
SQL error: Query failed (#20230331_083711_00014_ja35w): Unknown transaction ID: 4ad79c3d-0203-420b-9bfe-de19f66c07c6. Possibly expired? Commands ignored until end of transaction block
Why is Presto opening transactions for get metadata operations?
Description
I've noticed, Presto uses SQL transactions in metadata operations like
getTables
. Is it expected behavior? My configuration:0.278
,0.278
,autoCommit = false
,In my Cassandra catalog, I have two keyspaces that have the same name but different case like:
quoted
,QuoteD
.When I run
getTables(cassandra, quoted)
, I'm getting below error:More than one keyspace has been found for the case insensitive schema name: quoted -> (QuoteD, quoted)
That's ok, but when I try to do the same operation I'm getting:
SQL error: Query failed (#20230331_083711_00014_ja35w): Unknown transaction ID: 4ad79c3d-0203-420b-9bfe-de19f66c07c6. Possibly expired? Commands ignored until end of transaction block
Why is Presto opening transactions for get metadata operations?