SNOW-751897: Snowpark should warn if the given warehouse does not exist

[sfc-gh-jfreeberg]

Please answer these questions before submitting your issue. Thanks!

1. What version of Python are you using?

   3.8

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

macOS-13.2.1-arm64-arm-64bit

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

asn1crypto==1.5.1
attrs==22.2.0
black==23.1.0
certifi==2022.12.7
cffi==1.15.1
charset-normalizer==2.1.1
click==8.1.3
cloudpickle==2.0.0
cryptography==39.0.1
exceptiongroup==1.1.0
filelock==3.9.0
idna==3.4
iniconfig==2.0.0
mypy-extensions==1.0.0
oscrypto==1.3.0
packaging==23.0
pathspec==0.11.0
platformdirs==3.0.0
pluggy==1.0.0
pycparser==2.21
pycryptodomex==3.17
PyJWT==2.6.0
pyOpenSSL==23.0.0
pytest==7.2.1
pytz==2022.7.1
requests==2.28.2
snowflake-connector-python==3.0.0
snowflake-snowpark-python==1.1.0
tomli==2.0.1
typing-extensions==4.4.0
urllib3==1.26.14

4. What did you do?

I created a session but had a typo in my warehouse name (I used "wh_A" but should have used "wh_B"). The session object was created successfully without any mention that the specified warehouse actually does not exist. The queries then went on to fail with this message:

Failed to execute query [queryID: 01aaa8e8-0505-c9cb-0000-xxxxxxxx] REDACTED
000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

The error message isn't super applicable in this context, I can write session.sql('use warehouse wh_B').collect() but that's probably not the desired user experience. Therefore, I think it would be beneficial for users if we logged a warning-level message if the given WH could not be found when the session is created.

[sfc-gh-aalam]

This is a good feedback Jason. Our team will work on it soon.

[mmyers5]

+1 I just lost hours of my time trying to figure out why some of my sessions were failing to run queries while others were running fine, was too stubborn to declare a "use warehouse" command 🥲