[BUG]TruLens Saves Data in Previously Used Schema Despite Configuration to Use New Schema

[HannaHUp]

Bug Description
I was using the PUBLIC schema, and all the tables in the PUBLIC schema were created by TruLens. Now, I have created all the tables under the TRULENS schema and configured the session to use the TRULENS schema. However, despite confirming the active schema as TRULENS using the CURRENT_SCHEMA() query, TruLens still saves new data into the PUBLIC schema instead of the intended TRULENS schema.

I don’t want to move the old data into the new schema. I want the data in the PUBLIC schema to remain there while new data is saved in the TRULENS schema. What should I do to achieve this?

sf_settings = {
    'account': 'P',
    'database': 'da',
    'warehouse': 'OH',
    'role': 'T',
    'user': 'NG',
    'schema': 'TRULENS',
    'password': {'password': None},
    'paramstyle': 'qmark'
}

Environment:

snowflake-sqlalchemy version: 1.7.3
trulens-eval version: 1.3.2
LiteLLM version: 1.57.8
"python.version" : 3.11.11,
"python.connector.version" : 3.12.1,
"os.name" : Linux

Additional context
Add any other context about the problem here.