Add blog post for 2.10.0 #1052
Add blog post for 2.10.0 #1052
Conversation
|
|
||
| I'm happy to announce that Apache Airflow 2.10.0 is now available, bringing an array of noteworthy enhancements and new features that will greatly serve our community. | ||
|
|
||
| Apache Airflow 2.10.0 contains over 135 commits, which include 43 new features, 85 improvements, 43 bug fixes, and 26 documentation changes. |
There was a problem hiding this comment.
The numbers seem off. I need to figure out how to get the proper data.
There was a problem hiding this comment.
We normally just get the counts from the release notes. Close enough.
There was a problem hiding this comment.
I should clarify, we get the feature/improvement/etc numbers from the release notes. The commit count comes directly from git, sorta like the query to find the top contributors. 135 is definitely low.
There was a problem hiding this comment.
@jedcunningham I updated the count using git compare. PTAL
There was a problem hiding this comment.
My gut tells me you've swung too far in the other direction. Trying to get just core commits, roughly.
|
|
||
| I'm happy to announce that Apache Airflow 2.10.0 is now available, bringing an array of noteworthy enhancements and new features that will greatly serve our community. | ||
|
|
||
| Apache Airflow 2.10.0 contains over 135 commits, which include 43 new features, 85 improvements, 43 bug fixes, and 26 documentation changes. |
There was a problem hiding this comment.
We normally just get the counts from the release notes. Close enough.
|
Missing TI history! |
| 🚏 Constraints: https://github.com/apache/airflow/tree/constraints-2.10.0 | ||
|
|
||
|
|
||
| ## Hybrid Execution |
There was a problem hiding this comment.
I'd also like to write a blog post entirely for multi exec config, since there is some nuance and details there that's worth spelling out and having it on the website blog like this example. I have not created one before, should I just follow this PR as an example of how to do that? I have the content written already but would need to translate it into this formatting.
There was a problem hiding this comment.
Sorry, missed this. Yeah. Totally open to that and we can link to it here! We did that for setup/teardown in 2.7, if you need another example.
Co-authored-by: Niko Oliveira <onikolas@amazon.com>
utkarsharma2
force-pushed
the
2.10.0-blog-post
branch
from
d5e1687
to
6ea6bc5
Compare
Added it, PTAL. |
|
Missing DAG parsing button in UI? |
I added it here -
I added it under, |
| * 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. | ||
|
|
There was a problem hiding this comment.
Should we add Open Telemetry traces ? cc : @howardyoo
|
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
<#1052 (comment)>:
> +
+
+
+### 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.
+
+
+
+## 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
<#1052 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHZNLLUS7UNJUGNUJISWIUTZRKIYHAVCNFSM6AAAAABMGUN2W2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMZWHAZDKNBRGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Maybe you can propose a PR with description/ screenshots @howardyoo ? Also that might be useful segway to explain the OTEL provider capabilities (i.e. how they allow to extend traces). |
@vatsrahul1001 I have moved it to its own section. |
Yes, PRs with screenshots would be nice for us to use in the post. I will wait for the same. @howardyoo |
|
@utkarsharma2 can we document PR as well |
No description provided.