howardyoo commented on PR #1052:
URL: https://github.com/apache/airflow-site/pull/1052#issuecomment-2287756616

   Hi Jarek,
   yes we should!!
   
   Howard
   
   On Tue, Aug 13, 2024 at 6:25 PM Jarek Potiuk ***@***.***>
   wrote:
   
   > ***@***.**** commented on this pull request.
   > ------------------------------
   >
   > In landing-pages/site/content/en/blog/airflow-2.10.0/index.md
   > <https://github.com/apache/airflow-site/pull/1052#discussion_r1716090675>:
   >
   > > +
   > +![Render dataset conditions in graph view](render_dataset_conditions.png)
   > +
   > +### Dataset event info in DAG Graph
   > +For a DAG run, users can now view the dataset events connected to it 
directly in the graph view.
   > +
   > +![Dataset event info](dataset_info.png)
   > +
   > +## Additional new features
   > +
   > +Here are just a few interesting new features since there are too many to 
list in full:
   > +
   > +* Deferrable operators can now execute directly from the triggerer 
without needing to go through the worker. This is especially efficient for 
certain operators, like sensors, and can help teams save both time and money.
   > +* Airflow 2.10 introduces a new button for on-demand DAG reparsing.
   > +* Crucial executor logs are now integrated into the task logs. If the 
executor fails to start a task, the relevant error messages will be available 
in the task logs, simplifying the debugging process.
   > +
   >
   > Should we add Open Telemetry traces ? cc : @howardyoo
   > <https://github.com/howardyoo>
   >
   > —
   > Reply to this email directly, view it on GitHub
   > 
<https://github.com/apache/airflow-site/pull/1052#pullrequestreview-2236825411>,
   > or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/AHZNLLUS7UNJUGNUJISWIUTZRKIYHAVCNFSM6AAAAABMGUN2W2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMZWHAZDKNBRGE>
   > .
   > You are receiving this because you were mentioned.Message ID:
   > ***@***.***>
   >
   


-- 
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: [email protected]

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

Reply via email to