anandhimurali opened a new pull request, #38982: URL: https://github.com/apache/airflow/pull/38982
**Motivation** Currently, users need to write custom extractor inorder to add custom facets in the lineage events. Managing the entire extractor will be hard while users might just want to add few custom facets as per their needs. **Modifications** The `get_custom_facets` function in the OpenLineage provider is extended to fetch the Airflow config `AIRFLOW__OPENLINEAGE__CUSTOM_FACET_FUNCTIONS`, execute those functions and append their return values to the run facet of the lineage event generated by the Airflow extractor. **Result** This PR enables users to add custom factes to the lineage events by defining functions that return the custom facet and setting the fully qualified path to the functions as an Airflow config `AIRFLOW__OPENLINEAGE__CUSTOM_FACET_FUNCTIONS`. After this change, users need not write the complete extractor in order to add custom facet in the lineage event. **Configs documentation for `AIRFLOW__OPENLINEAGE__CUSTOM_FACET_FUNCTIONS`**  <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- Thank you for contributing! 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 committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> <!-- Please keep an empty line above the dashes. --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/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]
