Athena responses includes Number of Rows Affected "breaking" Auto-Scale in graphs

I am running queries to an AWS Athena instance and the results that are returned include an affected rows count at the end of the response. I am unable to see how I can turn this off Athena and I am curious if there is a way to deal with this on the Redash side of the solution.

Can you explain the issue a little more clearly? Is there a bug somewhere?

If I run this query to an AWS Athena instance:

SELECT FROM_UNIXTIME(FLOOR(to_unixtime(query_ts)/300) * 300) AS TIME,
       COUNT()/300 AS count

In the return I get the data which looks like this:

20/12/20 00:00	1,952	
20/12/20 00:05	2,292	
20/12/20 00:10	2,141	
20/12/20 00:15	2,249	
20/12/20 00:20	2,916	

The very last line in the data is a count of the number of rows that matched the query:

19/01/21 23:25	917	
19/01/21 23:30	888	
19/01/21 23:35	956	
19/01/21 23:40	918	
19/01/21 23:45	927	
19/01/21 23:50	868	
19/01/21 23:55	930	

I have not figured out a way to change my query or to adjust Athena so it will not return the count at the end, so I am wondering if there is a way to deal with this via Redash.

When I try to graph the data I would like to use Auto-scale, but since I have one post that is significantly larger than the rest Auto-scale is using that number as the max.

I would appreciate any help I can get.

best regards

I’m sorry for being dense but I still don’t see the issue. Are you saying that Redash is displaying 1,635,892 at the end of the tabular result?

When the last row is included the auto-scale function in the graph creates a graph that looks like this:

If I could somehow get rid of the last row the graph would and should look like this:

Once again, I know I’m being dense but you didn’t answer my question. Is Redash showing 1,635,92 on the table? This is critical to understanding how to fix this issue. Sorry to pester.

Yes, which is what is causing the auto-scale to not be able to figure out how to scale. No worries, I would just like to find a solution.

Thanks. It sounds like a bug in how the query runner returns results then. The summary line should not appear in the table visualization at all. And if it appears in the table then it will affect the other visualizations also.