ElasticSearch plugins in my maven project

Elastic Stack Elasticsearch
1

Hi

I've set up a ElasticSearch cluster that has a number of plugins installed.
Now I'm also setting up a test environment, where each JAVA test case will
start up its own ES Node. So I've configured my Maven pom with a
ElasticSearch dependency, and programmed my test case to use ES.

Now, if I want test using the plugins that are used in the "real"
environment, how do I do that? For example the BigDesk or Phonetic plugin.
I might want to graphically monitor my test during execution or test the
search behaviour using the phonetic plugin. How can I accomplish this so
that the plugins are used with the ES instance started by my test classes?

/Per

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

2

It's simple, the test classpath must contain the es-plugin.properties,
so a node can activate the plugin at node startup.

Check my test code for the JDBC river:

https://github.com/jprante/elasticsearch-river-jdbc/blob/master/src/test/java/org/elasticsearch/river/jdbc/strategy/simple/AbstractRiverNodeTest.java

Jörg

Am 22.02.13 11:25, schrieb Per Ekman:

Hi

I've set up a Elasticsearch cluster that has a number of plugins
installed. Now I'm also setting up a test environment, where each JAVA
test case will start up its own ES Node. So I've configured my Maven
pom with a Elasticsearch dependency, and programmed my test case to
use ES.

Now, if I want test using the plugins that are used in the "real"
environment, how do I do that? For example the BigDesk or Phonetic
plugin. I might want to graphically monitor my test during execution
or test the search behaviour using the phonetic plugin. How can I
accomplish this so that the plugins are used with the ES instance
started by my test classes?

/Per

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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

3

Thanks. I think I understand, but in the case of for example BigHead, where
I don't have the source, I guess I should define a dependency in maven,
right? And then reference the plugin in es-plugin.properties?

On Fri, Feb 22, 2013 at 12:05 PM, Jörg Prante joergprante@gmail.com wrote:

It's simple, the test classpath must contain the es-plugin.properties, so
a node can activate the plugin at node startup.

Check my test code for the JDBC river:

https://github.com/jprante/**elasticsearch-river-jdbchttps://github.com/jprante/elasticsearch-river-jdbc

https://github.com/jprante/**elasticsearch-river-jdbc/blob/**
master/src/test/java/org/**elasticsearch/river/jdbc/strategy/simple/
AbstractRiverNodeTest.javahttps://github.com/jprante/elasticsearch-river-jdbc/blob/master/src/test/java/org/elasticsearch/river/jdbc/strategy/simple/AbstractRiverNodeTest.java

Jörg

Am 22.02.13 11:25, schrieb Per Ekman:

Hi

I've set up a Elasticsearch cluster that has a number of plugins
installed. Now I'm also setting up a test environment, where each JAVA test
case will start up its own ES Node. So I've configured my Maven pom with a
Elasticsearch dependency, and programmed my test case to use ES.

Now, if I want test using the plugins that are used in the "real"
environment, how do I do that? For example the BigDesk or Phonetic plugin.
I might want to graphically monitor my test during execution or test the
search behaviour using the phonetic plugin. How can I accomplish this so
that the plugins are used with the ES instance started by my test classes?

/Per

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.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
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.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

4

To explain a little bit more:

I'm not looking at developing my own plugin that shall be used by an
Elasticsearch installation. My goal is to run a test environment, where
each test case is running a Java ES Node Client, and I want this client to
be run using a number of plugins

On Fri, Feb 22, 2013 at 12:35 PM, Per Ekman per.ekman@gmail.com wrote:

Thanks. I think I understand, but in the case of for example BigHead,
where I don't have the source, I guess I should define a dependency in
maven, right? And then reference the plugin in es-plugin.properties?

On Fri, Feb 22, 2013 at 12:05 PM, Jörg Prante joergprante@gmail.comwrote:

It's simple, the test classpath must contain the es-plugin.properties, so
a node can activate the plugin at node startup.

Check my test code for the JDBC river:

https://github.com/jprante/**elasticsearch-river-jdbchttps://github.com/jprante/elasticsearch-river-jdbc

https://github.com/jprante/**elasticsearch-river-jdbc/blob/**
master/src/test/java/org/**elasticsearch/river/jdbc/strategy/simple/
AbstractRiverNodeTest.javahttps://github.com/jprante/elasticsearch-river-jdbc/blob/master/src/test/java/org/elasticsearch/river/jdbc/strategy/simple/AbstractRiverNodeTest.java

Jörg

Am 22.02.13 11:25, schrieb Per Ekman:

Hi

I've set up a Elasticsearch cluster that has a number of plugins
installed. Now I'm also setting up a test environment, where each JAVA test
case will start up its own ES Node. So I've configured my Maven pom with a
Elasticsearch dependency, and programmed my test case to use ES.

Now, if I want test using the plugins that are used in the "real"
environment, how do I do that? For example the BigDesk or Phonetic plugin.
I might want to graphically monitor my test during execution or test the
search behaviour using the phonetic plugin. How can I accomplish this so
that the plugins are used with the ES instance started by my test classes?

/Per

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.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
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.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

5

I think I have managed to solve this. I'm able to create an index with a
"phonetic" analyzer by just stating
the elasticsearch-analysis-phonetic-dependency in my pom.xml.

On Fri, Feb 22, 2013 at 2:18 PM, Per Ekman per.ekman@gmail.com wrote:

To explain a little bit more:

I'm not looking at developing my own plugin that shall be used by an
Elasticsearch installation. My goal is to run a test environment, where
each test case is running a Java ES Node Client, and I want this client to
be run using a number of plugins

On Fri, Feb 22, 2013 at 12:35 PM, Per Ekman per.ekman@gmail.com wrote:

Thanks. I think I understand, but in the case of for example BigHead,
where I don't have the source, I guess I should define a dependency in
maven, right? And then reference the plugin in es-plugin.properties?

On Fri, Feb 22, 2013 at 12:05 PM, Jörg Prante joergprante@gmail.comwrote:

It's simple, the test classpath must contain the es-plugin.properties,
so a node can activate the plugin at node startup.

Check my test code for the JDBC river:

https://github.com/jprante/**elasticsearch-river-jdbchttps://github.com/jprante/elasticsearch-river-jdbc

https://github.com/jprante/**elasticsearch-river-jdbc/blob/**
master/src/test/java/org/**elasticsearch/river/jdbc/strategy/simple/
AbstractRiverNodeTest.javahttps://github.com/jprante/elasticsearch-river-jdbc/blob/master/src/test/java/org/elasticsearch/river/jdbc/strategy/simple/AbstractRiverNodeTest.java

Jörg

Am 22.02.13 11:25, schrieb Per Ekman:

Hi

I've set up a Elasticsearch cluster that has a number of plugins
installed. Now I'm also setting up a test environment, where each JAVA test
case will start up its own ES Node. So I've configured my Maven pom with a
Elasticsearch dependency, and programmed my test case to use ES.

Now, if I want test using the plugins that are used in the "real"
environment, how do I do that? For example the BigDesk or Phonetic plugin.
I might want to graphically monitor my test during execution or test the
search behaviour using the phonetic plugin. How can I accomplish this so
that the plugins are used with the ES instance started by my test classes?

/Per

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.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
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.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

6

Yes, it's easy as that, thanks to Maven dependency resolution. The
Elasticsearch Java plugins are distributed as JARs via the Maven central
repo, so adding them as a dependency in pom.xml is all you have to do to
get their es-plugin.properties on your classpath. For other plugins, you
may need to add other Maven repos in the pom.xml as well.

Jörg

Am 22.02.13 15:21, schrieb Per Ekman:

I think I have managed to solve this. I'm able to create an index with
a "phonetic" analyzer by just stating
the elasticsearch-analysis-phonetic-dependency in my pom.xml.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.