kacpermuda opened a new pull request, #60462: URL: https://github.com/apache/airflow/pull/60462
<!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> ## Documentation improvements for OpenLineage provider This PR improves the OpenLineage provider documentation with better organization and expanded content: - **spark.rst**: Added separate page for Spark integration, explaining that it's a separate entity from the Airflow provider and requires its own installation and configuration. - **macros.rst**: Expanded to be the central documentation for job hierarchy and macros, consolidating information about cross-job dependencies (TriggerDagRunOperator, API triggers, ExternalTaskSensor, Airflow Assets) and how OpenLineage handles job relationships in each scenario. - **troubleshooting.rst**: Added troubleshooting page with best practices and common errors, where users trying to debug OL problems can find helpful information. - **supported_classes.rst**: Added explanation of what "supported" means, clarifying that all operators emit basic lineage while "supported" operators provide additional operator-specific metadata. - **guides/structure.rst**: Added paragraph explaining the difference between the `openlineage-python` client package and the `apache-airflow-providers-openlineage` provider package. - **guides/developer.rst**: Added section about helper functions e.g. emit_openlineage_events_for_databricks_queries ## Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). -- 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]
