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

feat(ingestion) slack source v2 - now ingests all user and channels #12795

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jayacryl
Copy link
Collaborator

@jayacryl jayacryl commented Mar 5, 2025

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Mar 5, 2025
Copy link

codecov bot commented Mar 5, 2025

Codecov Report

Attention: Patch coverage is 0% with 172 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
...estion/src/datahub/ingestion/source/slack/slack.py 0.00% 172 Missing ⚠️

❌ Your patch check has failed because the patch coverage (0.00%) is below the target coverage (75.00%). You can increase the patch coverage or adjust the target coverage.

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Collaborator

@hsheth2 hsheth2 left a comment

Choose a reason for hiding this comment

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

Probably would be good to have some tests for this - particularly the user lookup logic / platform resource generation

blob=json.dumps(value.to_obj()).encode("utf-8"),
contentType=SerializedValueContentTypeClass.JSON,
schemaType=SerializedValueSchemaTypeClass.PEGASUS,
schemaRef=schema_type,
Copy link
Collaborator

Choose a reason for hiding this comment

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

I thought we had helpers for this stuff in PlatformResourceInfo or SerializedResourceValue - is there a reason we're not using that stuff

yield mcp.as_workunit()
else:
logger.error("Failed to fetch team information")
raise Exception("Failed to fetch team information")
Copy link
Collaborator

Choose a reason for hiding this comment

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

) and user_obj.real_name:
mutation_required = True
corpuser_editable_info.displayName = user_obj.real_name
if mutation_required:
Copy link
Collaborator

Choose a reason for hiding this comment

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

can we make a copy of the original corpuser_editable_info, and then we know a mutation is required if the two objects aren't equal

platform=DATA_PLATFORM_SLACK_URN, instance=self.id
)

def update_with_team_info(self, team_info: dict) -> None:
Copy link
Collaborator

Choose a reason for hiding this comment

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

why wouldn't we pass this stuff in as part of the SlackInstance constructor?

or alternatively, classmethod def from_slack_team_info(team_info: dict) -> SlackInstance

@datahub-cyborg datahub-cyborg bot added pending-submitter-response Issue/request has been reviewed but requires a response from the submitter and removed needs-review Label for PRs that need review from a maintainer. labels Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ingestion PR or Issue related to the ingestion of metadata pending-submitter-response Issue/request has been reviewed but requires a response from the submitter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants