[ 
https://issues.apache.org/jira/browse/BEAM-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699692#comment-16699692
 ] 

Kenneth Knowles commented on BEAM-6082:
---------------------------------------

Summarizing here:

 - The data for SQL Query 5 was being attributed to Query 4, which doesn't 
exist in SQL so it isn't on the dashboards.
 - The data for SQL Query 7 was being attributed to Query 5, and shows a 
straight line trend with no regression for production runners. There _is_ a 
massive regression on the Direct runner, which is expected due to immutability 
and encodeability enforcement. You can see this regression happened just before 
I broke the data reporting.

> [SQL] Nexmark 5, 7 time out
> ---------------------------
>
>                 Key: BEAM-6082
>                 URL: https://issues.apache.org/jira/browse/BEAM-6082
>             Project: Beam
>          Issue Type: Bug
>          Components: dsl-sql
>            Reporter: Anton Kedin
>            Assignee: Kenneth Knowles
>            Priority: Blocker
>             Fix For: 2.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> SQL Nexmark Queries 5 and 7 are timing out since around October 29: 
> [https://apache-beam-testing.appspot.com/explore?dashboard=5084698770407424] 
>  
> Current suspect is https://github.com/apache/beam/pull/6856



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to