snowflakedb / snowflakedb/snowpark-python

SNOW-857053: current_schemas() not really pythonic

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

Nobody has claimed this yet.

feature triaged
Dominant language
Python
Stars
341
Forks
155
Avg merge
4d 16h
Merged PRs (30d)
27

Description

Please answer these questions before submitting your issue. Thanks!

  1. What version of Python are you using?

3.8.17

  1. What operating system and processor architecture are you using?

macOS-13.4.1-arm64-arm-64bit

  1. What are the component versions in the environment (pip freeze)?

Irrelevant.

  1. What did you do?

Ran this:

 >>> session.create_dataframe([1]).select(functions.current_schemas()).collect()[0]["CURRENT_SCHEMAS()"]
'["MYDB.PUBLIC"]'
  1. What did you expect to see?

A list of schemas, not a string that should be evaluated.

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.

Research direction

Reproduce the reported session.create_dataframe([1]).select(functions.current_schemas()).collect() call in Python 3.8.17 on the stated environment, then inspect the current_schemas() function and result-conversion path. Done means the collected value is a Python list of schemas rather than a string representation that requires evaluation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, sql
Domain
database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.