Expose catalog and schema information from the connection string to the query history system table

Open
#524 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python, sql, sqlalchemy
Domain
backend-api-design, databases

Research direction

Trace how catalog and schema properties from the connection string are handled and how queries are submitted to the query history system table. Done means queries issued with JDBC or SQLAlchemy-provided defaults expose the selected catalog and schema in query history, with the representation decided consistently.

Written by the indexing model from the issue text.

Description

Request to expose jdbc / sqlalchemy provided catalog / schema properties in query history system table. Currently it lacks this information and it is not clear in a query select * from bla what table is queried.

A simple solution could be to provide append a comment to the query that specified the selected / default catalog and schema based on the connection string.

Dominant language
Python
Stars
233
Forks
152
Avg merge
21h 5m
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/databricks-sql-python

All issues in databricks/databricks-sql-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.