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

issue-18099: Edit Lineage Operation not working with isOwner() condition #19070

Merged
merged 2 commits into from
Dec 20, 2024

Conversation

harshach
Copy link
Collaborator

Describe your changes:

Fixes #18099

I worked on ... because ...

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@harshach
Copy link
Collaborator Author

harshach commented Dec 14, 2024

This requires review and few long runs from ingestion side and see if its impacting any lineage ingestions cc @harshsoni2024 @ulixius9
@karanh37 what test coverage we have from UI side while editing.
@Prajwal214 run some tests with customer use-cases here
@mohityadav766 and @Siddhanttimeline need a through review

Copy link

@harshach harshach merged commit 939f458 into main Dec 20, 2024
15 of 19 checks passed
@harshach harshach deleted the issue-18099 branch December 20, 2024 04:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend safe to test Add this label to run secure Github workflows on PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Edit Lineage Operation not working with isOwner() condition
2 participants