ito-kotei-ab

Here is the correct import . ``` const { createClient } = require('athena-client'); ... const client = createClient(this.clientConfig, this.awsConfig); ``` or ``` const athena = require('athena-client'); ... const client =...

Sorry for the late reply. It is the result of executing with the following sample. ``` const ctasClient = athena.createClient({ bucketUri: 'xxx', skipFetchResult: true, },{ region: 'xxx' }) ctasClient.execute("select 1",...

I thought that errors will be returned from aws sdk when the service limit is exceeded. https://docs.aws.amazon.com/athena/latest/ug/service-limits.html Is there documentation about Athena queuing query?

`tx` is created with `context.Backgroud` as an argument at the start. Is it the intended behavior that when the context of the `ExecContext` argument is canceled, the ExecContext rarely does...

Yes, I confirmed. Here is the result of executing the following code. ``` package main import ( "context" "database/sql" "errors" "fmt" "log" "sync" "time" _ "github.com/go-sql-driver/mysql" ) func main() {...

It's also understandable that running your SLEEP (4) will always result in an error. This is because the event reported this time only occurs when the context cacncels during defer...

If context is canceled during defer finish () after mc.Exec is successful, tx.ExecContext will treat the connection as a Bad Connection without returning an error.

Yes, that's right. For example, if you create a transaction for multiple destinations, you want to avoid Commit failure even though ExecContext succeeds. > By the way, I don't recommend...

I don't need a cacnel while executing a query, but I thought it would be better to check if it was cancel before executing the query.