zhongjiajie commented on a change in pull request #8633:
URL: https://github.com/apache/airflow/pull/8633#discussion_r417703490



##########
File path: UPDATING.md
##########
@@ -1164,6 +1164,55 @@ The goal of this change is to achieve a more consistent 
and configurale cascadin
 
 When initializing a Snowflake hook or operator, the value used for 
`snowflake_conn_id` was always `snowflake_conn_id`, regardless of whether or 
not you specified a value for it. The default `snowflake_conn_id` value is now 
switched to `snowflake_default` for consistency and will be properly overriden 
when specified.
 
+### Simplify the response payload of endpoints /dag_stats and /task_stats
+
+The response of endpoints `/dag_stats` and `/task_stats` help UI fetch brief 
statistics about DAGs and Tasks. The format was like
+
+```json
+{
+    "example_http_operator": [
+        {
+            "state": "success",
+            "count": 0,
+            "dag_id": "example_http_operator",
+            "color": "green"
+        },
+        {
+            "state": "running",
+            "count": 0,
+            "dag_id": "example_http_operator",
+            "color": "lime"
+        },
+        ...
+],
+...
+}
+```
+
+The `dag_id` was repeated in the payload, which makes the response payload 
unnecessarily bigger.
+
+Now the `dag_id` will not appear repeated in the payload, and the response 
format is like
+
+```json
+{
+    "example_http_operator": [
+        {
+            "state": "success",
+            "count": 0,
+            "color": "green"
+        },
+        {
+            "state": "running",
+            "count": 0,
+            "color": "lime"
+        },
+        ...
+],
+...
+}
+```
+
+

Review comment:
       ```suggestion
   
   ```




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to