Open christopherswenson opened 3 months ago
Could possibly solve this by generating a "Malloy Compile ID" (UUID) in either the translator or the Runtime API, which would get passed to all connection operations, allowing the connection to ensure that the same session was used for the entirety of a Malloy compile lifecycle.
There does not seem to be any system in place to make sure that, for a single Malloy compile, the Snowflake connection only uses one session. Because of this, when compiling a Malloy model, the Snowflake connection might persist a query result using one session, then attempt to access that saved result in a different session, which fails.
This is an example of such a failure
This seems to be relevant code
This is an example of a test that might exhibit this behavior