You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/04/06 09:43:52 UTC

[GitHub] [superset] sujiplr opened a new issue, #19555: Log table not showing the actual run time of the SQL .

sujiplr opened a new issue, #19555:
URL: https://github.com/apache/superset/issues/19555

   The duration_ms column in the log table suppose to log the exact duration of the SQL against the source database while loading the chart. But it's always showing the load time from cache to chart. In my case GAQ is enabled.
   
   #### How to reproduce the bug
   
   1. enable GAQ in deployment.
     global_async_settings: |
       GLOBAL_ASYNC_QUERIES_REDIS_STREAM_PREFIX = "async-events-"
       GLOBAL_ASYNC_QUERIES_REDIS_STREAM_LIMIT = 1000
       GLOBAL_ASYNC_QUERIES_REDIS_STREAM_LIMIT_FIREHOSE = 1000000
       GLOBAL_ASYNC_QUERIES_JWT_COOKIE_NAME = "async-token"
       GLOBAL_ASYNC_QUERIES_JWT_COOKIE_SECURE = False
       GLOBAL_ASYNC_QUERIES_JWT_COOKIE_DOMAIN = None
       GLOBAL_ASYNC_QUERIES_JWT_SECRET = "xxxxx"
       GLOBAL_ASYNC_QUERIES_TRANSPORT = "polling"
       GLOBAL_ASYNC_QUERIES_POLLING_DELAY = 1500
       GLOBAL_ASYNC_QUERIES_WEBSOCKET_URL = "ws://superset-websocket:8080/"
       GLOBAL_ASYNC_QUERIES_REDIS_CONFIG = {
           "port": env('REDIS_PORT'),
           "host": env('REDIS_HOST'),
           "password": "",
           "db": 0,
           "ssl": False,
       }
   
   2. Create a chart against a source database.
   3. Do the force refresh of the chart and check the logs table.
   4. Used below SQL in my case.
   
   select l.id,
             l.action,
             cast(l.dttm as date) dt,
             u.first_name,
             u.last_name,
             l.dttm,
             d.dashboard_title dashboard_name,
             s.slice_name slice_name,
             l.duration_ms,
             l.referrer
      from logs l
      inner join ab_user u on u.id=l.user_id
      left join dashboards d on l.dashboard_id=d.id
      left join slices s on l.slice_id=s.id
   order by id desc
   
   
   ### Environment
   
   (please complete the following information):
   
   - browser type and version:
   - superset version: `1.4.1`
   - python version: `python --version`
   - node.js version: `node -v`
   - any feature flags active:
    FEATURE_FLAGS = {
               "ALERT_REPORTS": True,
               'ENABLE_TEMPLATE_PROCESSING': True,
               "ENABLE_EXPLORE_DRAG_AND_DROP": True,
               "THUMBNAILS": True,
               'DASHBOARD_RBAC': True,
               'ROW_LEVEL_SECURITY': True,
               'OMNIBAR': True,
               'DASHBOARD_NATIVE_FILTERS_SET': True,
               'DASHBOARD_NATIVE_FILTERS': True,
               'DASHBOARD_CROSS_FILTERS': True,
               "GLOBAL_ASYNC_QUERIES": True,
               "ALLOW_FULL_CSV_EXPORT": True,
       }
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] rusackas commented on issue #19555: Log table not showing the actual run time of the SQL .

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #19555:
URL: https://github.com/apache/superset/issues/19555#issuecomment-1402791120

   This issue is in regards to a fairly old version of Superset, so I'm somewhat curious if you're still facing this in 2.0.1 or on `master`. 
   
   Also pinging @villebro for good measure since he's growing interested in the GAQ feature - I'll try to use labels on these issues if/when I spot them.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [I] Log table not showing the actual run time of the SQL . [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #19555: Log table not showing the actual run time of the SQL .
URL: https://github.com/apache/superset/issues/19555


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org