aws / aws/amazon-redshift-python-driver

Getting the query id from the cursor

Ouverte
#268 0 commentaires 2 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Python
Étoiles
220
Forks
86
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Hi - would it be possible to get the query id from the cursor instead of needing to run a separate query? Right now we have to make a separate call when we want to cancel the running query [like this](https://github.com/dbt-labs/dbt-adapters/blob/300ee9278b2568173c0c465399a69696cc085982/dbt-redshift/src/dbt/adapters/redshift/connections.py#L459) and would also like to easily log query ids in our application logs for customer debugging.

This is something that we get [from snowflake](https://github.com/dbt-labs/dbt-adapters/blob/b5d3fbf8b704e393d07b8f37371a9ebc7eb33e44/dbt-snowflake/src/dbt/adapters/snowflake/record/cursor/cursor.py#L19) but doesn't look like I can get it from the cursor here.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Compare the Redshift connection usage in dbt-redshift connections.py with the cursor implementation referenced in dbt-snowflake cursor.py. Trace how the Redshift cursor is created and where query execution exposes metadata; done means callers can obtain the query id from the cursor for cancellation and application logging without a separate query.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
aws, python
Domaine
databases
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
30/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.