Enabling different discovery plugin

Elastic Stack Elasticsearch
1

Hi there, I wrote plugins before, but I'm not getting how to extend the
discovery plugin. From the examples, it seems that once one extend
ZenDiscoveryModule bind the proper discovery to its own discovery, add the
proper UnicastHostProvider things should work. But I can't get my
discoverymodule to load:

in the config I have:

discovery:
type: custom

And:

CustomDiscoveryModule extends ZenDiscoveryModule
CustomDiscover extends ZenDiscover
CustomUnicastHostProvider implements UnicastHostsProvider

I have one plugin just to load the plugin, I tried to add the
CustomDiscoveryModule on the modules list but I got an error saying binding
for that interface had already happened.

My best guess is that when set the type of discovery, ES uses some form of
naming convention to load the class, but this does not seems to be
happening.

Any suggestions on where to look next?

Regards

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/18785746-17c7-4467-a904-753bb938fd77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Extra space on my yml :frowning:

Thanks

On Friday, April 10, 2015 at 3:51:11 PM UTC-4, Vinicius Carvalho wrote:

Hi there, I wrote plugins before, but I'm not getting how to extend the
discovery plugin. From the examples, it seems that once one extend
ZenDiscoveryModule bind the proper discovery to its own discovery, add the
proper UnicastHostProvider things should work. But I can't get my
discoverymodule to load:

in the config I have:

discovery:
type: custom

And:

CustomDiscoveryModule extends ZenDiscoveryModule
CustomDiscover extends ZenDiscover
CustomUnicastHostProvider implements UnicastHostsProvider

I have one plugin just to load the plugin, I tried to add the
CustomDiscoveryModule on the modules list but I got an error saying binding
for that interface had already happened.

My best guess is that when set the type of discovery, ES uses some form of
naming convention to load the class, but this does not seems to be
happening.

Any suggestions on where to look next?

Regards

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b7e2f257-d6b3-4b42-93e4-b8dad48b2a32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

Package name is important here.
Have a look at aws cloud plugin If you need code example BTW.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 10 avr. 2015 à 21:51, Vinicius Carvalho viniciusccarvalho@gmail.com a écrit :

Hi there, I wrote plugins before, but I'm not getting how to extend the discovery plugin. From the examples, it seems that once one extend ZenDiscoveryModule bind the proper discovery to its own discovery, add the proper UnicastHostProvider things should work. But I can't get my discoverymodule to load:

in the config I have:

discovery:
type: custom

And:

CustomDiscoveryModule extends ZenDiscoveryModule
CustomDiscover extends ZenDiscover
CustomUnicastHostProvider implements UnicastHostsProvider

I have one plugin just to load the plugin, I tried to add the CustomDiscoveryModule on the modules list but I got an error saying binding for that interface had already happened.

My best guess is that when set the type of discovery, ES uses some form of naming convention to load the class, but this does not seems to be happening.

Any suggestions on where to look next?

Regards

You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/18785746-17c7-4467-a904-753bb938fd77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/31812B1A-DD11-4354-949F-BB7708F89571%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.