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

DruidBeams: Respect druid.discovery.curator.path in fromConfig. #151

Merged
merged 1 commit into from Mar 18, 2016

Conversation

gianm
Copy link
Member

@gianm gianm commented Mar 16, 2016

Fixes #150.

@fjy
Copy link
Member

fjy commented Mar 16, 2016

👍

@nishantmonu51
Copy link
Member

Can this break things for anyone who has already set druid.discovery.curator.path in their config but defaults were being used prior to this change?

@gianm
Copy link
Member Author

gianm commented Mar 18, 2016

In theory yes, although if someone set druid.discovery.curator.path to something wrong then that's kind of strange. But, yes, that could happen.

btw, till now this property was respected for Server and Kafka, but not Core (i.e. DruidBeams.fromConfig).

@nishantmonu51
Copy link
Member

+1, Added release notes label so that we dont forget to mention this.

nishantmonu51 added a commit that referenced this pull request Mar 18, 2016
DruidBeams: Respect druid.discovery.curator.path in fromConfig.
@nishantmonu51 nishantmonu51 merged commit b57ada0 into druid-io:master Mar 18, 2016
@KurtYoung
Copy link

Can you release a SNAPSHOT version for this issue? We are stuck with this issue or do you have any way to workaround with 0.7.4?

@KurtYoung
Copy link

never mind, i built a 0.7.5-SNAPSHOT myself :-)

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.

None yet

4 participants