This message was deleted.

It isn't clear why you would need a released version of druid. The console is part of the distribution that you will build from your branch. You can also do the console integration later on.

@Abhishek Agarwal Thanks for the reply, we were tinkering with the released version of druid because this tutorial: https://druid.apache.org/docs/latest/development/extensions.html Talks about adding an extension package into the druid.extensions.loadlist within the common.runtime.properties file of the released druid. But this didnt work for us since the release druid doesn't have our web console changes for pravega. Is there a similar loadlist feature within the druid source code such that when we launch the web console via

npm start

we can load from our pravega extension?

can you raise a draft PR? For web-console-related changes, @Vadim is the best person to help.

you could try building a release package by doing

mvn -Pdist,skip-static-checks,skip-tests -Dmaven.javadoc.skip=true -q -T1C clean install

and then looking in the

distribution/target/

folder for a tarball

From what you said it looks like your dev web console is connecting to the druid server just fine (the dev server starts on

0.0.0.0:18081

and proxies requests to

druid_host:8888

) but you need to have the correct extension loaded in your dev environment

@Gian Merlino Thanks for pointing us to that release package command! I think that is what we were looking for. We tried creating release versions but at the moment we have some errors when running./bin/start-druid where there are failures connecting to overlord, historical etc. We will continue tinkering with this command to see if we can build a successfull build version thank you