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

[auto-pick-to-release-3.6]feat: more datasets introduced #472

Merged
merged 1 commit into from
Feb 22, 2023

Conversation

github-actions[bot]
Copy link

What type of PR is this?

  • bug
  • feature
  • enhancement

What problem(s) does this PR solve?

Issue(s) number: #441

Description:

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Cherry-pick from vesoft-inc/nebula-studio#470

* feat: more datasets introduced

partially-implement: #441

- [x] basketballplayer (need to add serve edge)
- [x] SNS https://www.siwei.io/nebulagraph-sns/
- [x] data lineage https://www.siwei.io/data-lineage-oss-ref-solution/
- [x] recommendation system https://www.siwei.io/recommendation-system-with-graphdb/ https://www.siwei.io/nebulagraph-etl-dbt/
- [x] id mapping/entity resolution https://www.siwei.io/identity-resolution/
- [x] fraud detection https://www.siwei.io/fraud-detection-with-nebulagraph/
- [x] OpenStack (AI Ops) https://www.siwei.io/graph-enabled-infra-ops/
- [x] FIFA 2022 https://www.siwei.io/chatgpt-and-nebulagraph-predict-fifa-world-cup/

* resize movie dataset

* chore: refine the naming of space data lineage

* revert change on server/api/studio/etc/studio-api.yaml
Copy link
Contributor

@hetao92 hetao92 left a comment

Choose a reason for hiding this comment

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

LGTM

@hetao92 hetao92 merged commit 88f5965 into release-3.6 Feb 22, 2023
@hetao92 hetao92 deleted the auto-pick-470-to-release-3.6 branch February 22, 2023 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants