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

logging(cli): dropping neo4j message to debug to avoid confusion #7340

Merged
merged 1 commit into from
Feb 14, 2023

Conversation

shirshanka
Copy link
Contributor

The original log message in the cli was added when DataHub's default graph backend was neo4j and we wanted to make sure that people were in the know when we selected elastic by default for them.

1.5 yrs later: people are actually more confused about this message and wonder whether they should instead be using neo4j and why.

Example: https://datahubspace.slack.com/archives/CV2KB471C/p1676324646452419

This PR drops that message to debug level.

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 Feb 14, 2023
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants