Modularization of elastic search on maven central


(Frédéric Camblor) #1

Hi everyone :slight_smile:

I was simply wondering if it was planned to modularize the elastic search
artefact present on maven central ?
For now, the org.elasticsearch:elasticsearch:0.17.4 takes approximatively
11Mo.

I'm only using the java client API and I'm wondering if the full 11Mo bundle
are useful for the java api only ?
Will you plan to lower this and provide a much thiner archive ("a la"
spring) allowing to choose which component to integrate in our application ?

Thanks in advance for your feedback :slight_smile:

Frédéric


(Shay Banon) #2

Yea..., its a hefty jar... . The main reason why the jar is a big one is
because elasticsearch is almost completely evented. This menas a lot of
small, sometimes inner classes, and Java does a bad job compressing it (its
zip based, compression is per class file).

Another smaller reason is that elasticsearch embeds most of the libs it uses
(except for Lucene), this include mainly jackson, netty, and guice. This
allows for elasticsearch to use its own verified version of those libraries.

So, to answer your question, no, there won't be a smaller jar file in the
future.

2011/8/5 Frédéric Camblor fcamblor@gmail.com

Hi everyone :slight_smile:

I was simply wondering if it was planned to modularize the elastic search
artefact present on maven central ?
For now, the org.elasticsearch:elasticsearch:0.17.4 takes approximatively
11Mo.

I'm only using the java client API and I'm wondering if the full 11Mo
bundle are useful for the java api only ?
Will you plan to lower this and provide a much thiner archive ("a la"
spring) allowing to choose which component to integrate in our application ?

Thanks in advance for your feedback :slight_smile:

Frédéric


(Roberto Franchini) #3

On Fri, Aug 5, 2011 at 9:36 PM, Shay Banon kimchy@gmail.com wrote:
[cut]

So, to answer your question, no, there won't be a smaller jar file in the
future.

Hi,
I'm evaluating ES. I understand your needs, but could you split the
client part of the jar from the server part?
Is it possible to do that without a lot of effort?
Cheers,
RF

Roberto Franchini
L'impossibile è inevitabile.



Tel +39.011.562.71.15
jabber:ro.franchini@gmail.com skype:ro.franchini


(Shay Banon) #4

It will require a lot of effort, and will not reduce the size by much...

On Tue, Aug 9, 2011 at 7:45 PM, Roberto Franchini franchini@celi.it wrote:

On Fri, Aug 5, 2011 at 9:36 PM, Shay Banon kimchy@gmail.com wrote:
[cut]

So, to answer your question, no, there won't be a smaller jar file in the
future.

Hi,
I'm evaluating ES. I understand your needs, but could you split the
client part of the jar from the server part?
Is it possible to do that without a lot of effort?
Cheers,
RF

Roberto Franchini
L'impossibile è inevitabile.
http://www.celi.it
http://www.blogmeter.it
Tel +39.011.562.71.15
jabber:ro.franchini@gmail.com skype:ro.franchini


(system) #5