-
Notifications
You must be signed in to change notification settings - Fork 1
Add first implementation of stacks according to ADR 21 #32
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks quite good! I'm doing some manual testing now. It would be great to have some kuttl tests for this I think.
stacks/druid-superset/druid.yaml
Outdated
metadataStorageDatabase: | ||
dbType: derby | ||
connString: jdbc:derby://localhost:1527/var/druid/metadata.db;create=true | ||
host: localhost # TODO why do i need to specify this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is not ideal, I think in the near future we want to have a common "SQLConnection" object to use instead of this
I ran the superset-druid-s3 stack and it works for me too 👍 |
Lars will invite for a brief discussion on this today |
Thanks for the review and confirmation that it works :) |
I proudly present the first working stack:
druid-superset-s3
Use the following command to spin it up
releases.yaml
is currently a bit hacky, as we haven't released operators for so long...