Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Airbyte ol integration #40689

Closed
wants to merge 4 commits into from
Closed

Conversation

Imbruced
Copy link
Member


Add open lineage data from airbyte operator

This mr aims to add ol support for airbyte operator. It adds schema and column level lineage and simple statistics with number rows. Code is tested with unit tests and also manually verified using local apache airflow instance.
PR is using v2 version of ol objects but OperatorLineage is only working with v1 version, so its locked until migration. What I understand it's blocked by this mr #39530.

Copy link

boring-cyborg bot commented Jul 10, 2024

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: dev@airflow.apache.org
    Slack: https://s.apache.org/airflow-slack

@Imbruced
Copy link
Member Author

WIP

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this file under hook directory?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to keep it close the place where validation happens :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but this is not a hook... it's confusing.
Some users may not even know what OL is or what this file is about.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on hook methods (validation is making sure the schema is ok for connection output). I am not pushing to keep it there, where do you think is the best place to put it ? Thanks

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets hear from @mobuchowski as I assume this isn't just about Airbyte but for any other integration

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be the best to put in under utils IMO, it's not really tied to particular hook other than "code proximity".

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be the best to put in under utils IMO, it's not really tied to particular hook other than "code proximity".


valid_connection = is_connection_valid(res.json())
if not valid_connection:
self.log.warning("Connection is not valid")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be best to explain more in the warning what means that connection is not valid - unless this is something well known by Airbyte users - who I am not 🙂

@Imbruced Imbruced force-pushed the airbyte-ol-integration branch 3 times, most recently from 5c69a75 to 8cf05fb Compare July 29, 2024 07:27
@Imbruced Imbruced force-pushed the airbyte-ol-integration branch 2 times, most recently from ad16faf to 4f7db51 Compare July 29, 2024 12:24
Signed-off-by: pawelkocinski <pawel93kocinski@gmail.com>
Signed-off-by: pawelkocinski <pawel93kocinski@gmail.com>
Signed-off-by: pawelkocinski <pawel93kocinski@gmail.com>
Signed-off-by: pawelkocinski <pawel93kocinski@gmail.com>
@marcosmarxm
Copy link
Contributor

@lmaczulajtys can this wait until #41122 get done? I'm trying to replace the API auth method and start using the official Python API SDK to run all operations.

Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Sep 24, 2024
@github-actions github-actions bot closed this Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:providers provider:airbyte stale Stale PRs per the .github/workflows/stale.yml policy file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants