flask_log.current_user set to None in SQL_QUERY_MUTATOR while using SQLLab about superset HOT 3 CLOSED

Hey there, @dmarkey! I'm here to help you with any bugs, questions, or contributions you have for Apache Superset. Let's tackle this issue together!

The issue you're encountering with flask_login.current_user being None during the execution of SQL_QUERY_MUTATOR in SQLLab sessions is due to differences in the execution context between SQLLab and navigating graphs. In SQLLab sessions, the user ID is explicitly retrieved and stored in the SqlJsonExecutionContext class using the get_user_id() function, rather than relying on flask_login.current_user directly ^[1].

To work around this, you can modify your SQL_QUERY_MUTATOR to use the get_user_id() function to retrieve the user ID. Here’s an example:

from superset.utils.core import get_user_id

def SQL_QUERY_MUTATOR(sql: str, **kwargs) -> str:
    user_id = get_user_id()
    print(user_id)  # This should print the correct user ID during a SQLLab session
    return sql

This approach ensures that you get the correct user information even in the SQLLab context.

To continue talking to Dosu, mention @dosu.

from superset.

That actually works.. first time I've been impressed by AI.

from superset.

closing

from superset.