Problem Compiling an Internal Gradle Release

[Wolf]

Hi,

I am using a Japanese language analyzer with jar files that I have imported to compile a new Analyzer provider with new type in the AnalysisModule processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module dependencies for elastic search and all builds well.

I have tested the analyzers with index and type map scripts successfully and on indexing documents but I am unable to build a distribution package with the command ./gradlew release or ./gradle in the elasticsearch directory. Consistently I get errors indicating that the jar files for the analyzer are missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory ~/.gradle/cache but I still get errors in fact I tried to use the syntax in the dependecies section of the build.gradle file for lucene however I get errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete the release build?

Regards,

Wolf

[Wolf_2]

Hi,

I am using a Japanese language analyzer with jar files that I have
imported to compile a new AnalyzerProvider with new type in the
AnalysisModule processAnalyzers method and the constructor of the
IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project
Module dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts
successfully and on indexing documents but I am unable to build a
distribution package with the command ./gradlew release or ./gradlew
in the elasticsearch directory. Consistently I get errors indicating
that the jar files for the analyzer are missing however a build in the
Intellij environment is successful and interprets index, type map,
document and faceted search scripts correctly.

I took measures to include the jar libraries in the GRADLE_HOME
directory ~/.gradle/cache but I still get errors in fact I tried to
use the syntax in the dependecies section of the build.gradle file for
lucene however I get errors since there is no maven/2 repository for
these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and
complete the release build?

Regards,

Wolf

On Mar 15, 3:14 pm, wolfkden wolfk...@sprintmail.com wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have imported
to compile a new Analyzer provider with new type in the AnalysisModule
processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module
dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts successfully and
on indexing documents but I am unable to build a distribution package with
the command ./gradlew release or ./gradle in the elasticsearch directory.
Consistently I get errors indicating that the jar files for the analyzer are
missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory
~/.gradle/cache but I still get errors in fact I tried to use the syntax in
the dependecies section of the build.gradle file for lucene however I get
errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete
the release build?

Regards,

Wolf

--
View this message in context:http://elasticsearch-users.115913.n3.nabble.com/Problem-Compiling-an-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

[kimchy (Shay Banon)]

Heya,

Are you trying to build a custom analyzer? In this case, I would not spend time in trying to adapt to elasticsearch build system, just write the plugin / extension in your favorite build tool / IDE, and link to the elasticsearch distribution jar.

-shay.banon
On Wednesday, March 16, 2011 at 12:23 AM, Wolf wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have
imported to compile a new AnalyzerProvider with new type in the
AnalysisModule processAnalyzers method and the constructor of the
IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project
Module dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts
successfully and on indexing documents but I am unable to build a
distribution package with the command ./gradlew release or ./gradlew
in the elasticsearch directory. Consistently I get errors indicating
that the jar files for the analyzer are missing however a build in the
Intellij environment is successful and interprets index, type map,
document and faceted search scripts correctly.

I took measures to include the jar libraries in the GRADLE_HOME
directory ~/.gradle/cache but I still get errors in fact I tried to
use the syntax in the dependecies section of the build.gradle file for
lucene however I get errors since there is no maven/2 repository for
these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and
complete the release build?

Regards,

Wolf

On Mar 15, 3:14 pm, wolfkden wolfk...@sprintmail.com wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have imported
to compile a new Analyzer provider with new type in the AnalysisModule
processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module
dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts successfully and
on indexing documents but I am unable to build a distribution package with
the command ./gradlew release or ./gradle in the elasticsearch directory.
Consistently I get errors indicating that the jar files for the analyzer are
missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory
~/.gradle/cache but I still get errors in fact I tried to use the syntax in
the dependecies section of the build.gradle file for lucene however I get
errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete
the release build?

Regards,

Wolf

--
View this message in context:http://elasticsearch-users.115913.n3.nabble.com/Problem-Compiling-an-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

[Wolf_2]

Thank you for the response Shay,

I have coded and compiled a an analysis plugin module that references the
Elasticsearch jar. How do I integrate it with the existing Elasticsearch
execution environment. I am using ICU as a template but I notice that
Elasticsearch requires a plugin install to run ICU.

I have had an extension of elasticsearch running for several days in
Intellij but when I make a distribution it is missing gradle references to 2
jar files. I just need to include these to get the distribution working and
deploy it on my cluster.

I could use instruction on plugin deployment procedures or including
additional jar files in my internal elasticsearch distribution.

Thank you for your support.

Regards,

Wolf

On Tue, Mar 15, 2011 at 4:15 PM, Shay Banon shay.banon@elasticsearch.comwrote:

Heya,

Are you trying to build a custom analyzer? In this case, I would not
spend time in trying to adapt to elasticsearch build system, just write the
plugin / extension in your favorite build tool / IDE, and link to the
elasticsearch distribution jar.

-shay.banon

On Wednesday, March 16, 2011 at 12:23 AM, Wolf wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have
imported to compile a new AnalyzerProvider with new type in the
AnalysisModule processAnalyzers method and the constructor of the
IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project
Module dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts
successfully and on indexing documents but I am unable to build a
distribution package with the command ./gradlew release or ./gradlew
in the elasticsearch directory. Consistently I get errors indicating
that the jar files for the analyzer are missing however a build in the
Intellij environment is successful and interprets index, type map,
document and faceted search scripts correctly.

I took measures to include the jar libraries in the GRADLE_HOME
directory ~/.gradle/cache but I still get errors in fact I tried to
use the syntax in the dependecies section of the build.gradle file for
lucene however I get errors since there is no maven/2 repository for
these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and
complete the release build?

Regards,

Wolf

On Mar 15, 3:14 pm, wolfkden wolfk...@sprintmail.com wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have imported
to compile a new Analyzer provider with new type in the AnalysisModule
processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module
dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts successfully
and
on indexing documents but I am unable to build a distribution package with
the command ./gradlew release or ./gradle in the elasticsearch directory.
Consistently I get errors indicating that the jar files for the analyzer
are
missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory
~/.gradle/cache but I still get errors in fact I tried to use the syntax in
the dependecies section of the build.gradle file for lucene however I get
errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete
the release build?

Regards,

Wolf

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Problem-Compiling-an-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

[kimchy (Shay Banon)]

Hi,

I don't think that for a custom analyzer plugin you need to create your own elasticsearch distribution. Plugins are simple, and are just jar files including the es-plugin.properties in the root of the classpath/jar.

If you extract the icu plugin, you will see that it just includes jar files that automatically get included in the classpath when elasticsearch is started. The es-plugin.properties is used to detect which plugin to load.

So, if you create an external project, link to elasticsearch jar, and create your own jar of your analysis plugin, you can simple create a directory under plugins and drop the jar file there (and any other jar files that are needed). They will automatically be loaded to the classpath and the plugin will be instantiated based on the es-plugin.properties content.
On Wednesday, March 16, 2011 at 9:53 PM, Wolfgang Kraske wrote:

Thank you for the response Shay,

I have coded and compiled a an analysis plugin module that references the Elasticsearch jar. How do I integrate it with the existing Elasticsearch execution environment. I am using ICU as a template but I notice that Elasticsearch requires a plugin install to run ICU.

I have had an extension of elasticsearch running for several days in Intellij but when I make a distribution it is missing gradle references to 2 jar files. I just need to include these to get the distribution working and deploy it on my cluster.

I could use instruction on plugin deployment procedures or including additional jar files in my internal elasticsearch distribution.

Thank you for your support.

Regards,

Wolf

On Tue, Mar 15, 2011 at 4:15 PM, Shay Banon shay.banon@elasticsearch.com wrote:

Heya,

Are you trying to build a custom analyzer? In this case, I would not spend time in trying to adapt to elasticsearch build system, just write the plugin / extension in your favorite build tool / IDE, and link to the elasticsearch distribution jar.

-shay.banon
On Wednesday, March 16, 2011 at 12:23 AM, Wolf wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have
imported to compile a new AnalyzerProvider with new type in the
AnalysisModule processAnalyzers method and the constructor of the
IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project
Module dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts
successfully and on indexing documents but I am unable to build a
distribution package with the command ./gradlew release or ./gradlew
in the elasticsearch directory. Consistently I get errors indicating
that the jar files for the analyzer are missing however a build in the
Intellij environment is successful and interprets index, type map,
document and faceted search scripts correctly.

I took measures to include the jar libraries in the GRADLE_HOME
directory ~/.gradle/cache but I still get errors in fact I tried to
use the syntax in the dependecies section of the build.gradle file for
lucene however I get errors since there is no maven/2 repository for
these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and
complete the release build?

Regards,

Wolf

On Mar 15, 3:14 pm, wolfkden wolfk...@sprintmail.com wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have imported
to compile a new Analyzer provider with new type in the AnalysisModule
processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module
dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts successfully and
on indexing documents but I am unable to build a distribution package with
the command ./gradlew release or ./gradle in the elasticsearch directory.
Consistently I get errors indicating that the jar files for the analyzer are
missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory
~/.gradle/cache but I still get errors in fact I tried to use the syntax in
the dependecies section of the build.gradle file for lucene however I get
errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete
the release build?

Regards,

Wolf

--
View this message in context:http://elasticsearch-users.115913.n3.nabble.com/Problem-Compiling-an-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

[Wolf_2]

I did create a plugin and tested it with the 0.15.2 release.

I can create a google code release for Elasticsearch if you would like.

All in all though I still would like to know more about gradle.

Also I noticed that you do not have an avro transport. Avro uses JSON rather
than the fixed coded types of Thrift so the Elasticsearch community may be
interested.

I have been using thrift for the time being however since I believe you have
recommended thrift over curl to other users as the most efficient transport.
Let me know here if I am on the right track.

Regards,

Wolf

On Thu, Mar 17, 2011 at 2:24 AM, Shay Banon shay.banon@elasticsearch.comwrote:

Hi,

I don't think that for a custom analyzer plugin you need to create your
own elasticsearch distribution. Plugins are simple, and are just jar files
including the es-plugin.properties in the root of the classpath/jar.

If you extract the icu plugin, you will see that it just includes jar
files that automatically get included in the classpath when elasticsearch is
started. The es-plugin.properties is used to detect which plugin to load.

So, if you create an external project, link to elasticsearch jar, and
create your own jar of your analysis plugin, you can simple create a
directory under plugins and drop the jar file there (and any other jar files
that are needed). They will automatically be loaded to the classpath and the
plugin will be instantiated based on the es-plugin.properties content.

On Wednesday, March 16, 2011 at 9:53 PM, Wolfgang Kraske wrote:

Thank you for the response Shay,

I have coded and compiled a an analysis plugin module that references the
Elasticsearch jar. How do I integrate it with the existing Elasticsearch
execution environment. I am using ICU as a template but I notice that
Elasticsearch requires a plugin install to run ICU.

I have had an extension of elasticsearch running for several days in
Intellij but when I make a distribution it is missing gradle references to 2
jar files. I just need to include these to get the distribution working and
deploy it on my cluster.

I could use instruction on plugin deployment procedures or including
additional jar files in my internal elasticsearch distribution.

Thank you for your support.

Regards,

Wolf

On Tue, Mar 15, 2011 at 4:15 PM, Shay Banon shay.banon@elasticsearch.comwrote:

Heya,

Are you trying to build a custom analyzer? In this case, I would not
spend time in trying to adapt to elasticsearch build system, just write the
plugin / extension in your favorite build tool / IDE, and link to the
elasticsearch distribution jar.

-shay.banon

On Wednesday, March 16, 2011 at 12:23 AM, Wolf wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have
imported to compile a new AnalyzerProvider with new type in the
AnalysisModule processAnalyzers method and the constructor of the
IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project
Module dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts
successfully and on indexing documents but I am unable to build a
distribution package with the command ./gradlew release or ./gradlew
in the elasticsearch directory. Consistently I get errors indicating
that the jar files for the analyzer are missing however a build in the
Intellij environment is successful and interprets index, type map,
document and faceted search scripts correctly.

I took measures to include the jar libraries in the GRADLE_HOME
directory ~/.gradle/cache but I still get errors in fact I tried to
use the syntax in the dependecies section of the build.gradle file for
lucene however I get errors since there is no maven/2 repository for
these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and
complete the release build?

Regards,

Wolf

On Mar 15, 3:14 pm, wolfkden wolfk...@sprintmail.com wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have imported
to compile a new Analyzer provider with new type in the AnalysisModule
processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module
dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts successfully
and
on indexing documents but I am unable to build a distribution package with
the command ./gradlew release or ./gradle in the elasticsearch directory.
Consistently I get errors indicating that the jar files for the analyzer
are
missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory
~/.gradle/cache but I still get errors in fact I tried to use the syntax in
the dependecies section of the build.gradle file for lucene however I get
errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete
the release build?

Regards,

Wolf

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Problem-Compiling-an-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

[kimchy (Shay Banon)]

Why do you want to create a google code release of elasticsearch? I don't really understand. Do you want to get your analyzer plugin committed to elasticsearch repo? What does it do?

Avro is another option for serialization + transport, yes. As far as I know last time I looked at Avro, the transport part was lacking.
On Friday, March 18, 2011 at 8:12 AM, Wolfgang Kraske wrote:

I did create a plugin and tested it with the 0.15.2 release.

I can create a google code release for Elasticsearch if you would like.

All in all though I still would like to know more about gradle.

Also I noticed that you do not have an avro transport. Avro uses JSON rather than the fixed coded types of Thrift so the Elasticsearch community may be interested.

I have been using thrift for the time being however since I believe you have recommended thrift over curl to other users as the most efficient transport. Let me know here if I am on the right track.

Regards,

Wolf

On Thu, Mar 17, 2011 at 2:24 AM, Shay Banon shay.banon@elasticsearch.com wrote:

Hi,

I don't think that for a custom analyzer plugin you need to create your own elasticsearch distribution. Plugins are simple, and are just jar files including the es-plugin.properties in the root of the classpath/jar.

If you extract the icu plugin, you will see that it just includes jar files that automatically get included in the classpath when elasticsearch is started. The es-plugin.properties is used to detect which plugin to load.

So, if you create an external project, link to elasticsearch jar, and create your own jar of your analysis plugin, you can simple create a directory under plugins and drop the jar file there (and any other jar files that are needed). They will automatically be loaded to the classpath and the plugin will be instantiated based on the es-plugin.properties content.
On Wednesday, March 16, 2011 at 9:53 PM, Wolfgang Kraske wrote:

Thank you for the response Shay,

I have coded and compiled a an analysis plugin module that references the Elasticsearch jar. How do I integrate it with the existing Elasticsearch execution environment. I am using ICU as a template but I notice that Elasticsearch requires a plugin install to run ICU.

I have had an extension of elasticsearch running for several days in Intellij but when I make a distribution it is missing gradle references to 2 jar files. I just need to include these to get the distribution working and deploy it on my cluster.

I could use instruction on plugin deployment procedures or including additional jar files in my internal elasticsearch distribution.

Thank you for your support.

Regards,

Wolf

On Tue, Mar 15, 2011 at 4:15 PM, Shay Banon shay.banon@elasticsearch.com wrote:

Heya,

Are you trying to build a custom analyzer? In this case, I would not spend time in trying to adapt to elasticsearch build system, just write the plugin / extension in your favorite build tool / IDE, and link to the elasticsearch distribution jar.

-shay.banon
On Wednesday, March 16, 2011 at 12:23 AM, Wolf wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have
imported to compile a new AnalyzerProvider with new type in the
AnalysisModule processAnalyzers method and the constructor of the
IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project
Module dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts
successfully and on indexing documents but I am unable to build a
distribution package with the command ./gradlew release or ./gradlew
in the elasticsearch directory. Consistently I get errors indicating
that the jar files for the analyzer are missing however a build in the
Intellij environment is successful and interprets index, type map,
document and faceted search scripts correctly.

I took measures to include the jar libraries in the GRADLE_HOME
directory ~/.gradle/cache but I still get errors in fact I tried to
use the syntax in the dependecies section of the build.gradle file for
lucene however I get errors since there is no maven/2 repository for
these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and
complete the release build?

Regards,

Wolf

On Mar 15, 3:14 pm, wolfkden wolfk...@sprintmail.com wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have imported
to compile a new Analyzer provider with new type in the AnalysisModule
processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module
dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts successfully and
on indexing documents but I am unable to build a distribution package with
the command ./gradlew release or ./gradle in the elasticsearch directory.
Consistently I get errors indicating that the jar files for the analyzer are
missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory
~/.gradle/cache but I still get errors in fact I tried to use the syntax in
the dependecies section of the build.gradle file for lucene however I get
errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete
the release build?

Regards,

Wolf

--
View this message in context:http://elasticsearch-users.115913.n3.nabble.com/Problem-Compiling-an-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

[Eks_Dev]

Avro is another option for serialization + transport, yes. As far as I know
last time I looked at Avro, the transport part was lacking.

Avro at the moment looks like ti would fit nicely to ES, look at the
"Netty-based Java RPC server", there is also http transport.

Avro is json-friendly, and has some really cool features like "avro
data file" (ES transaction log?). E.g. Hadoop map reduce can work with
"avro data files"...

I do not know if streaming support is already there, but I am sure as
a hell it is going to be there soon as hadoop needs it.

[kimchy (Shay Banon)]

The problem is not the RPC server, its the clients.
On Friday, March 18, 2011 at 10:21 AM, eks dev wrote:

Avro is another option for serialization + transport, yes. As far as I know

last time I looked at Avro, the transport part was lacking.

Avro at the moment looks like ti would fit nicely to ES, look at the
"Netty-based Java RPC server", there is also http transport.

Avro is json-friendly, and has some really cool features like "avro
data file" (ES transaction log?). E.g. Hadoop map reduce can work with
"avro data files"...

I do not know if streaming support is already there, but I am sure as
a hell it is going to be there soon as hadoop needs it.

[Wolf_2]

The Igo Japanese analyzer is a winner with my Japanese clients in comparison
to the CJK and SmartChinese analyzers for east Asian characters. Both of the
aforementioned do not parse words correctly, create extra words from
character combinations (context insensitive) and shreds western
words mercilessly.

On Fri, Mar 18, 2011 at 12:02 AM, Shay Banon
shay.banon@elasticsearch.comwrote:

Why do you want to create a google code release of elasticsearch? I don't
really understand. Do you want to get your analyzer plugin committed to
elasticsearch repo? What does it do?

Avro is another option for serialization + transport, yes. As far as I know
last time I looked at Avro, the transport part was lacking.

On Friday, March 18, 2011 at 8:12 AM, Wolfgang Kraske wrote:

I did create a plugin and tested it with the 0.15.2 release.

I can create a google code release for Elasticsearch if you would like.

All in all though I still would like to know more about gradle.

Also I noticed that you do not have an avro transport. Avro uses JSON
rather than the fixed coded types of Thrift so the Elasticsearch community
may be interested.

I have been using thrift for the time being however since I believe you
have recommended thrift over curl to other users as the most efficient
transport. Let me know here if I am on the right track.

Regards,

Wolf

On Thu, Mar 17, 2011 at 2:24 AM, Shay Banon shay.banon@elasticsearch.comwrote:

Hi,

I don't think that for a custom analyzer plugin you need to create your
own elasticsearch distribution. Plugins are simple, and are just jar files
including the es-plugin.properties in the root of the classpath/jar.

If you extract the icu plugin, you will see that it just includes jar
files that automatically get included in the classpath when elasticsearch is
started. The es-plugin.properties is used to detect which plugin to load.

So, if you create an external project, link to elasticsearch jar, and
create your own jar of your analysis plugin, you can simple create a
directory under plugins and drop the jar file there (and any other jar files
that are needed). They will automatically be loaded to the classpath and the
plugin will be instantiated based on the es-plugin.properties content.

On Wednesday, March 16, 2011 at 9:53 PM, Wolfgang Kraske wrote:

Thank you for the response Shay,

I have coded and compiled a an analysis plugin module that references the
Elasticsearch jar. How do I integrate it with the existing Elasticsearch
execution environment. I am using ICU as a template but I notice that
Elasticsearch requires a plugin install to run ICU.

I have had an extension of elasticsearch running for several days in
Intellij but when I make a distribution it is missing gradle references to 2
jar files. I just need to include these to get the distribution working and
deploy it on my cluster.

I could use instruction on plugin deployment procedures or including
additional jar files in my internal elasticsearch distribution.

Thank you for your support.

Regards,

Wolf

On Tue, Mar 15, 2011 at 4:15 PM, Shay Banon <shay.banon@elasticsearch.com

wrote:

Heya,

Are you trying to build a custom analyzer? In this case, I would not
spend time in trying to adapt to elasticsearch build system, just write the
plugin / extension in your favorite build tool / IDE, and link to the
elasticsearch distribution jar.

-shay.banon

On Wednesday, March 16, 2011 at 12:23 AM, Wolf wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have
imported to compile a new AnalyzerProvider with new type in the
AnalysisModule processAnalyzers method and the constructor of the
IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project
Module dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts
successfully and on indexing documents but I am unable to build a
distribution package with the command ./gradlew release or ./gradlew
in the elasticsearch directory. Consistently I get errors indicating
that the jar files for the analyzer are missing however a build in the
Intellij environment is successful and interprets index, type map,
document and faceted search scripts correctly.

I took measures to include the jar libraries in the GRADLE_HOME
directory ~/.gradle/cache but I still get errors in fact I tried to
use the syntax in the dependecies section of the build.gradle file for
lucene however I get errors since there is no maven/2 repository for
these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and
complete the release build?

Regards,

Wolf

On Mar 15, 3:14 pm, wolfkden wolfk...@sprintmail.com wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have
imported
to compile a new Analyzer provider with new type in the AnalysisModule
processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module
dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts successfully
and
on indexing documents but I am unable to build a distribution package with
the command ./gradlew release or ./gradle in the elasticsearch directory.
Consistently I get errors indicating that the jar files for the analyzer
are
missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory
~/.gradle/cache but I still get errors in fact I tried to use the syntax
in
the dependecies section of the build.gradle file for lucene however I get
errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete
the release build?

Regards,

Wolf

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Problem-Compiling-an-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

[kimchy (Shay Banon)]

I see, and its open source so sure, it can be an "official" plugin for elasticsearch. Just fork elasticsearch at github, push your changes, and I can have a look at what fails and help fix it.
On Friday, March 18, 2011 at 10:45 AM, Wolfgang Kraske wrote:

The Igo Japanese analyzer is a winner with my Japanese clients in comparison to the CJK and SmartChinese analyzers for east Asian characters. Both of the aforementioned do not parse words correctly, create extra words from character combinations (context insensitive) and shreds western words mercilessly.

On Fri, Mar 18, 2011 at 12:02 AM, Shay Banon shay.banon@elasticsearch.com wrote:

Why do you want to create a google code release of elasticsearch? I don't really understand. Do you want to get your analyzer plugin committed to elasticsearch repo? What does it do?

Avro is another option for serialization + transport, yes. As far as I know last time I looked at Avro, the transport part was lacking.
On Friday, March 18, 2011 at 8:12 AM, Wolfgang Kraske wrote:

I did create a plugin and tested it with the 0.15.2 release.

I can create a google code release for Elasticsearch if you would like.

All in all though I still would like to know more about gradle.

Also I noticed that you do not have an avro transport. Avro uses JSON rather than the fixed coded types of Thrift so the Elasticsearch community may be interested.

I have been using thrift for the time being however since I believe you have recommended thrift over curl to other users as the most efficient transport. Let me know here if I am on the right track.

Regards,

Wolf

On Thu, Mar 17, 2011 at 2:24 AM, Shay Banon shay.banon@elasticsearch.com wrote:

Hi,

I don't think that for a custom analyzer plugin you need to create your own elasticsearch distribution. Plugins are simple, and are just jar files including the es-plugin.properties in the root of the classpath/jar.

If you extract the icu plugin, you will see that it just includes jar files that automatically get included in the classpath when elasticsearch is started. The es-plugin.properties is used to detect which plugin to load.

So, if you create an external project, link to elasticsearch jar, and create your own jar of your analysis plugin, you can simple create a directory under plugins and drop the jar file there (and any other jar files that are needed). They will automatically be loaded to the classpath and the plugin will be instantiated based on the es-plugin.properties content.
On Wednesday, March 16, 2011 at 9:53 PM, Wolfgang Kraske wrote:

Thank you for the response Shay,

I have coded and compiled a an analysis plugin module that references the Elasticsearch jar. How do I integrate it with the existing Elasticsearch execution environment. I am using ICU as a template but I notice that Elasticsearch requires a plugin install to run ICU.

I have had an extension of elasticsearch running for several days in Intellij but when I make a distribution it is missing gradle references to 2 jar files. I just need to include these to get the distribution working and deploy it on my cluster.

I could use instruction on plugin deployment procedures or including additional jar files in my internal elasticsearch distribution.

Thank you for your support.

Regards,

Wolf

On Tue, Mar 15, 2011 at 4:15 PM, Shay Banon shay.banon@elasticsearch.com wrote:

Heya,

Are you trying to build a custom analyzer? In this case, I would not spend time in trying to adapt to elasticsearch build system, just write the plugin / extension in your favorite build tool / IDE, and link to the elasticsearch distribution jar.

-shay.banon
On Wednesday, March 16, 2011 at 12:23 AM, Wolf wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have
imported to compile a new AnalyzerProvider with new type in the
AnalysisModule processAnalyzers method and the constructor of the
IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project
Module dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts
successfully and on indexing documents but I am unable to build a
distribution package with the command ./gradlew release or ./gradlew
in the elasticsearch directory. Consistently I get errors indicating
that the jar files for the analyzer are missing however a build in the
Intellij environment is successful and interprets index, type map,
document and faceted search scripts correctly.

I took measures to include the jar libraries in the GRADLE_HOME
directory ~/.gradle/cache but I still get errors in fact I tried to
use the syntax in the dependecies section of the build.gradle file for
lucene however I get errors since there is no maven/2 repository for
these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and
complete the release build?

Regards,

Wolf

On Mar 15, 3:14 pm, wolfkden wolfk...@sprintmail.com wrote:

Hi,

I am using a Japanese language analyzer with jar files that I have imported
to compile a new Analyzer provider with new type in the AnalysisModule
processAnalyzers method and the constructor of the IndicesAnalysisService.

I have included dependency references in the IDEA Intellij Project Module
dependencies for Elasticsearch and all builds well.

I have tested the analyzers with index and type map scripts successfully and
on indexing documents but I am unable to build a distribution package with
the command ./gradlew release or ./gradle in the elasticsearch directory.
Consistently I get errors indicating that the jar files for the analyzer are
missing however a build in the Intellij environment is successful.

I took measures to include the jar libraries in the GRADLE_HOME directory
~/.gradle/cache but I still get errors in fact I tried to use the syntax in
the dependecies section of the build.gradle file for lucene however I get
errors since there is no maven/2 repository for these analyzer libraries.

Any quick work arounds to get ./gradlew to find the jar files and complete
the release build?

Regards,

Wolf

--
View this message in context:http://elasticsearch-users.115913.n3.nabble.com/Problem-Compiling-an-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.