Details
-
Task
-
Resolution: Fixed
-
Major
-
4.0.3
-
None
-
None
-
1
-
SDK45
Description
If someone sets PYCBC_LOG_LEVEL in environment variables (and doesn't explicitly configure python logging), we should create a console logger in the cxx client and set the level appropriately. Oddly, I thought I did this, but apparently not.
Lets check for this when we create a connection object - first check to see if there's a logger already. If not, and PYCBC_LOG_LEVEL is set, make the console logger and set the level. Similarly, if we are using python logging, we need to check to see if the logger already exists and raise an exception so the user knows that the logger has to be set before ever making the first connection in cases where the PYCBC_LOG_LEVEL is set. Simple enough.
Attachments
Issue Links
- relates to
-
PYCBC-1403 Crash at shutdown when using python logging
- Open
For Gerrit Dashboard: PYCBC-1402 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
182226,2 | PYCBC-1402: Add support for PYCBC_LOG_LEVEL env variable | master | couchbase-python-client | Status: MERGED | +2 | +1 |