-
Notifications
You must be signed in to change notification settings - Fork 43
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
OpenLineage: Rename the name and namespace along with URI #1306
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Codecov ReportBase: 95.00% // Head: 94.99% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1306 +/- ##
==========================================
- Coverage 95.00% 94.99% -0.02%
==========================================
Files 71 71
Lines 3304 3315 +11
Branches 381 381
==========================================
+ Hits 3139 3149 +10
- Misses 101 102 +1
Partials 64 64
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
c82cd84
to
c603c1d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@rajaths010494 @JDarDagran is the |
Actually why do you need this format:
with two slashes before dataset name? The path should be absolute so I'd rather see URI as This spec, 3.3. Path explains more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually why do you need this format:
f"{self.input_data.openlineage_dataset_namespace()}" f"://{self.input_data.openlineage_dataset_name()}"
with two slashes before dataset name? The path should be absolute so I'd rather see URI as
file://172.26.0.2:22/tmp/sqlite.db.top_animation
.This spec, 3.3. Path explains more.
@rajaths010494 we should do this change across.
Yeah saw i will make the necessary changes |
Does this look fine. @JDarDagran @sunank200 . If yes i will make the necessary changes. |
👍 |
9cced6c
to
b8a8296
Compare
…/astronomer/astro-sdk into rename-localfilesystem-namespace
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rajaths010494 Change looks good to me.But lets add the test for this change.
We should create a method for URI for each database and use that. I will do that change and push it |
LGTM |
Describe the bug - There have been new conventions introduced: [Naming.md#local-file-system](https://github.com/OpenLineage/OpenLineage/blob/main/spec/Naming.md#local-file-system) I believe sqlite counts as local file, therefore you could adjust naming convention in astro as well. A word of explanation: both IP and port are mandatory. It means that if port is unknown (e. g. if file exists in Airflow's local file system only) you should default to some value. In one of OL extractors it is defaulted to paramiko.config.SSH_PORT, in most cases it's equal to 22. Reference: #1142 (comment) - Add openlineage_dataset_uri() method to create URI as per each database. closes #1281 Co-authored-by: Ankit Chaurasia <8670962+sunank200@users.noreply.github.com> (cherry picked from commit b725430)
Describe the bug
I believe sqlite counts as local file, therefore you could adjust naming convention in astro as well.
A word of explanation: both IP and port are mandatory. It means that if port is unknown (e. g. if file exists in Airflow's local file system only) you should default to some value. In one of OL extractors it is defaulted to paramiko.config.SSH_PORT, in most cases it's equal to 22.
Reference: #1142 (comment)
closes #1281