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

KH-539: Add default Superset datasets #73

Merged
merged 5 commits into from
Jun 18, 2024
Merged

KH-539: Add default Superset datasets #73

merged 5 commits into from
Jun 18, 2024

Conversation

enyachoke
Copy link
Contributor

@enyachoke enyachoke commented Jun 13, 2024

As a follow-up to initial work on https://mekomsolutions.atlassian.net/browse/KH-539, we needed to bring in some default datasets and database connection.

@enyachoke enyachoke requested a review from rbuisson June 13, 2024 05:03
offset: 0
cache_timeout: null
schema: public
sql: 'SELECT * FROM concepts '
Copy link
Contributor

@Ruhanga Ruhanga Jun 13, 2024

Choose a reason for hiding this comment

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

Thanks for the PR @enyachoke, do we however need to consume these datasets, or these are somewhat place holders/example dataset configs (apart from the database config)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We don't have to, but if we have any datasets which could conflict, we need to make sure we sync them up.

Copy link
Contributor

Choose a reason for hiding this comment

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

Remove the trailing space in the SELECT * FROM concepts
@Ruhanga , yes, those are the default ones that will come with Ozone anyway.

Copy link
Contributor

@rbuisson rbuisson left a comment

Choose a reason for hiding this comment

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

Some changes requested.

Additionally, I have push on upstream the asset/ folder and create a Maven sub-module. Could you update your PR with the changes?

@@ -0,0 +1,16 @@
database_name: PostgreSQL
Copy link
Contributor

Choose a reason for hiding this comment

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

@enyachoke this database should probably be named "Analytics", isn't it?
and should we update the file name to reflect that as well?

@enyachoke enyachoke merged commit 60784cb into main Jun 18, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants