I encounter a very strange issue with a query, which provides a different result at each run, but should not.
The problem can be reduced down to this query:
, my_python_udf() AS x
SELECT CURRENT_DATE AS created_at
UNION SELECT CURRENT_DATE - 1
UNION SELECT CURRENT_DATE - 2
ORDER BY T.created_at DESC
Executing this query today (Oct 3rd) will first lead to "Oct 3rd" then "Oct 1st" then "Oct 2nd" for example, and then the "Oct 1st" - "Oct 2nd" - "Oct 3rd", and then the expected result: "Oct 3rd" - "Oct 2nd" "Oct 1st" etc.... with no pattern (sometimes two consecutive runs will provide the same result)
my_python_udf is a Python UDF than can be, for example:
CREATE OR REPLACE FUNCTION my_python_udf()
STRICT IMMUTABLE RUNTIME_VERSION='3.8'
Here's more information about my config:
- Google Chrome 105.0.5195.125 (Official Build) (x86_64)
- OS: macOS Version 11.6.2 (Build 20G314)
- Metabase version: 0.44.0
- DB: Snowflake
I would really appreciate some pointers, as this is blocking us to build a dashboard.
Metabase has up to 15 connections (by default) to run queries on, so unless your variable is available to all connection sessions, then you'll see different results.
Thanks a lot @flamber. I do appreciate the interest in my question.
I'm not sure to follow though:
- What variable are you referring to exactly?
- Have you noticed that the function here always returns 1, no matter what connection we'd be using?
- Also, did you see that we're ordering independently of the output of the function (ORDER BY T.created_at)
Even if it was related to MB connections, that would remain a bug, right?
@HJ_alan I was busy with other things and barely looked at anything, just looked like the typical "my variable changes on each request".
So you are saying that the problem on occurs on Metabase and you cannot see similar problem with any other JDBC based applications?
To figure out if the problem is frontend or backend, then first have a look at the request response in your browser developer Network-tab.
Haha no worries @jamber, thanks again for looking into this.
It looks like a backend issue:
you cannot see similar problem with any other JDBC based applications?
I do observe the problem with Metabase and when querying with PyCharm.
I do NOT observe the problem from the Snowflake console, or when using
snowflake.connector in Python.
@HJ_alan I think you should contact Snowflake and report the problem, since it seems to be specific to their JDBC driver (it's not the first time they've had problems only with their Java connector).
Will do. Do you confirm this is just the response you get from Snowflake?
@HJ_alan I don't have an account, where I can create a function, so I cannot test.
I opened a ticket with Snowflake